dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2026-48814

CRITICAL · 9.1 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Network-AI is a TypeScript/Node.js multi-agent orchestrator. In versions 5.7.1 and earlier, the MCP SSE server allows unauthenticated cross-origin MCP tool invocation due to an empty default secret. This issue was partially addressed by CVE-2026-46701 in version 5.4.5 by closing the CORS flaw (with Access-Control-Allow-Origin now set only for localhost origins), but the empty-default-secret flaw described in the title remained: the SSE MCP server still defaulted to an empty secret, _isAuthorized() still returned true when the secret was empty, and a non-loopback bind only produced a warning. As a result, the server still ran fully unauthenticated by default. Any non-browser caller (for example, curl, SSRF, or a 0.0.0.0 bind) could invoke all 22 MCP tools (config_set, agent_spawn, blackboard_write, token_*) with no credentials. This issue was fixed in version 5.7.2.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Network-AI MCP SSE server in versions 5.7.1 and earlier uses an empty default secret, causing the _isAuthorized() function to always return true when no secret is configured. Combined with non-loopback bind warnings that don't prevent startup, this allows any caller (curl, SSRF, or 0.0.0.0 bind) to invoke all 22 MCP tools (config_set, agent_spawn, blackboard_write, token_*) without any authentication, resulting in full system compromise.

MitigationUpgrade to Network-AI version 5.7.2 or later, which addresses the empty default secret issue and enforces proper authentication.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Network-AI MCP SSE server version
    Check the installed package version using your package manager (npm, pip, or binary version flag like --version), or inspect the server's startup banner for the version number
    Affected if Version is 5.7.1 or earlier
  2. Verify if authentication secret is configured
    Examine the server's configuration file or environment variables for a configured secret value. Look for fields like 'secret', 'api_key', 'auth_token', or similar authentication parameters. An empty or unset value indicates the vulnerability.
    Affected if No secret is configured or the secret field is empty/null
  3. Check server bind address configuration
    Review the server startup configuration or logs to determine the bind address. Look for 'bind', 'host', or 'address' settings in config files or command-line arguments
    Affected if Server binds to 0.0.0.0 (all interfaces) instead of 127.0.0.1 or localhost, making it network-accessible
  4. Test unauthorized tool access
    Send an unauthenticated request to one of the MCP endpoints (e.g., config_set, agent_spawn, blackboard_write, or any token_* endpoint) using curl or similar tool without providing any Authorization header
    Affected if The request succeeds and returns valid tool response without any authentication credentials, indicating _isAuthorized() returns true unconditionally

Your environment is affected if the Network-AI MCP SSE server version is 5.7.1 or earlier AND no authentication secret is configured, especially if the server binds to a non-loopback address accessible to other callers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Network-AI version 5.7.2 or later, which addresses the empty default secret issue and enforces proper authentication.

Recommended fix High confidence

5.7.2

  1. 1. Identify the current Network-AI package version in your project (check package.json or installed version)
  2. 2. Upgrade to version 5.7.2 by running: npm install [email protected] (or yarn add [email protected])
  3. 3. Verify the upgrade was successful by running npm list network-ai or checking the installed version
  4. 4. Restart the MCP SSE server to load the patched version
  5. 5. Confirm the fix: verify that empty secrets are no longer accepted and _isAuthorization() no longer returns true for empty secrets

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48814 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-48814 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data