Live › vulnerability › CVE-2026-57207
Go to dashboardNetBox MCP Server, a read-only Model Context Protocol server for NetBox, has no authentication on its HTTP transport before version 1.2.1. Anyone who can reach the port gets a valid MCP session and can use all four NetBox tools, reading NetBox data without a token.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Teams running NetBox MCP Server with the HTTP transport on a version before 1.2.1 are exposed, especially where the port is reachable beyond the intended AI clients. Deployments using the stdio transport or running only on a locked-down local host are less exposed. The sources do not say how many deployments are reachable from the internet.
No product ranges from the sources yet.
grep TRANSPORT in the server's environment or config and look for TRANSPORT=http1.2.11.2.1 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-57207")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.