{"answers":{"affected":"2 open source packages ship an affected version, including network-ai.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48814 exists.","fix":"Upgrade network-ai to 5.7.2 or later.","what":"CVE-2026-48814 is a critical authentication bypass vulnerability in Jovancoding Network-AI, published on 17 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-48814 and fix it if it is affected.\n\nWhat it is: CVE-2026-48814 is a critical authentication bypass vulnerability in Jovancoding Network-AI, published on 17 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48814 exists.\n\nAffected packages and fixed versions:\n- network-ai (npm): affected all versions; fixed in 5.7.2\n- network-ai (npm): affected all versions; fixed in 5.7.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-48814/ (Markdown: https://insights.sbomify.com/CVE-2026-48814/index.md)","id":"CVE-2026-48814","markdown":"https://insights.sbomify.com/CVE-2026-48814/index.md","name":"CVE-2026-48814","record":{"aliases":["GHSA-r78r-rwrf-rjwp"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js AI orchestrator","requires_auth":"none","summary":"Attackers can invoke all MCP tools without credentials due to an empty default secret, enabling unauthorized control and potential code execution.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Network-AI: Empty default secret still authorizes all requests (Incomplete fix for CVE-2026-46701)","id":"CVE-2026-48814","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"sigstore-js: `certificateOIDs` verification constraints are silently dropped and never enforced","id":"CVE-2026-48815"},"packages":[{"ecosystem":"npm","fixed":["5.7.2"],"introduced":["0"],"last_affected":[],"package":"network-ai","purl":null,"source":"GHSA-r78r-rwrf-rjwp"},{"ecosystem":"npm","fixed":["5.7.2"],"introduced":["0"],"last_affected":[],"package":"network-ai","purl":"pkg:npm/network-ai","source":"GHSA-r78r-rwrf-rjwp"}],"prev":{"headline":"Flawfinder output manipulation via untrusted filenames and source text","id":"CVE-2026-48813"},"products":["Network-AI"],"published":"2026-06-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-18","vendors":["Jovancoding"]},"summary":"Attackers can invoke all MCP tools without credentials due to an empty default secret, enabling unauthorized control and potential code execution.","url":"https://insights.sbomify.com/CVE-2026-48814/"}