---
id: "CVE-2026-57207"
kind: "vulnerability"
aliases: ["CVE-2026-57207"]
title: "NetBox MCP Server: HTTP endpoint lacks authentication, exposing all NetBox tools"
severity: "medium"
cvss: 5.9
epss: 0.00415
exploited: false
status: "open"
category: "ai-tooling"
products: []
ecosystems: []
tags: ["ai-tooling", "mcp", "netbox", "python", "self-hosted"]
not_affected_if: ["patched-1.2.1", "port-not-reachable", "stdio-transport"]
published_at: "2026-10-23T14:17:56+00:00"
first_seen_at: "2026-10-23T21:57:34+00:00"
updated_at: "2026-10-25T12:38:49+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-57207", "first_seen_at": "2026-10-23T21:57:34+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-57207", "first_seen_at": "2026-10-25T12:38:49+00:00"}]
---

# NetBox MCP Server: HTTP endpoint lacks authentication, exposing all NetBox tools

NetBox 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, check and fix written by a model from the sources; labelled as such._

## How to check

- Run `grep TRANSPORT` in the server's environment or config and look for `TRANSPORT=http`
- Check the installed netbox-mcp-server version and see whether it is below `1.2.1`
- Check whether the MCP port is reachable from networks beyond the intended clients

## Fix

- Upgrade the NetBox MCP Server to `1.2.1` or later
- Until upgraded, restrict the MCP HTTP port with a firewall or bind it to localhost, or use a different transport

## Timeline

- 2026-10-23T21:57:34+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-57207
- 2026-10-25T12:38:49+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-57207

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_