CVE-2026-57207 NetBox MCP Server: HTTP transport exposes all NetBox data without authentication
Medium 5.9
Published
Updated
Check this codebase for CVE-2026-57207 and fix it if it is affected.
What it is: CVE-2026-57207 is a medium-severity vulnerability in netboxlabs netbox-mcp-server, published on 23 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-57207 in the wild and no public exploit code.
Affected product: netboxlabs netbox-mcp-server. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-57207/ (Markdown: https://insights.sbomify.com/CVE-2026-57207/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-57207?
CVE-2026-57207 is a medium-severity vulnerability in netboxlabs netbox-mcp-server, published on 23 Oct 2026.
Official description
NetBox MCP Server is a simple read-only Model Context Protocol server for NetBox. Prior to version 1.2.1, when running with TRANSPORT=http, the MCP server has no authentication on the HTTP endpoint. Any client that can reach the port gets a valid MCP session and full access to all four NetBox tools - no token or credential needed. This issue has been patched in version 1.2.1.
Which versions are affected by CVE-2026-57207?
How do I fix CVE-2026-57207?
No fix has been published for CVE-2026-57207 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-57207 being exploited?
There is no known exploitation of CVE-2026-57207 in the wild and no public exploit code.
Sources
Also known as GHSA-5qg7-j8mr-9477.