NetBox MCP Server: HTTP transport exposes all NetBox data without authentication
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.2.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The NetBox MCP Server, a read-only Model Context Protocol server for the NetBox network documentation tool, is affected when it runs in HTTP transport mode. Because its HTTP endpoint requires no authentication, anyone who can reach the port can open a session and read all NetBox data through its tools.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original 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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- netboxlabs netbox-mcp-server
fixed in 1.2.1