Quick answers
- Is CVE-2026-57207 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-57207 being exploited in the wild.
- How severe is CVE-2026-57207?
- Medium severity, with a CVSS score of 5.9, published 23 October 2026.
- Which products and versions are affected?
- NetBox Labs NetBox MCP Server < 1.2.1.
- Is there a fix for CVE-2026-57207?
- Yes: fixed in 1.2.1. Until then: Set the MCP_AUTH_TOKEN environment variable to require a Bearer token on all HTTP requests, ensuring all clients must provide Authorization: Bearer <token> headers to access the endpoint. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-57207 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-57207?
- Check whether you run NetBox Labs NetBox MCP Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 1.2.1
Set the MCP_AUTH_TOKEN environment variable to require a Bearer token on all HTTP requests, ensuring all clients must provide Authorization: Bearer <token> headers to access the endpoint.
Technical details
The HTTP transport endpoint lacks authentication because the FastMCP library only enforces auth when mcp.auth is explicitly set, which this project never does. An unauthenticated attacker can obtain a valid MCP session and access all four NetBox tools (netbox_get_objects, netbox_get_object_by_id, netbox_get_changelogs, netbox_search_objects) to enumerate and exfiltrate the full database. The vulnerability is especially critical because the README documentation recommends running with HOST=0.0.0.0, exposing the service network-wide by default.
Affected products
- NetBox Labs NetBox MCP Server < 1.2.1
Timeline
- 2026-06-18: disclosed
- 2026-06-17: patched