CVE-2026-55637 GeiserX CVE debrief

Who should care

Defenders responsible for securing GenieACS deployments should assess exposure and prioritize verification of the MCP_AUTH_TOKEN configuration and /mcp listener security. This includes reviewing CPE management state, monitoring for suspicious activity, and ensuring that the /mcp listener is properly secured.

Why it matters

CVE-2026-55637 is a vulnerability in the genieacs-mcp MCP server for GenieACS that allows an unauthenticated /mcp listener on the default MCP_LISTEN_ADDR value 127.0.0.1:8080 when MCP_AUTH_TOKEN is unset. Defenders should prioritize verifying the MCP_AUTH_TOKEN configuration and ensuring that the /mcp listener is properly secured.

• Potential exposure of CPE management state
• Possible modification of device configurations
• Risk of unauthorized device reboots
• Need for verification of MCP_AUTH_TOKEN configuration

Technical summary

The Streamable HTTP transport in cmd/server/main.go creates an unauthenticated /mcp listener on the default MCP_LISTEN_ADDR value 127.0.0.1:8080 when MCP_AUTH_TOKEN is unset and the httpSrv.Start(addr) branch does not validate the Host or Origin headers. This allows a malicious website to use DNS rebinding to send browser requests with attacker-controlled Host and Origin values to the loopback listener, initialize an MCP session, list tools, and invoke operations against the GenieACS NBI configured by ACS_URL. Successful exploitation can expose or modify CPE management state, including device reboots, firmware tasks, TR-069 parameter changes, presets, provisions, tags, connection requests, and task operations.

Defensive priority

Defenders should prioritize verifying the MCP_AUTH_TOKEN configuration and ensuring that the /mcp listener is properly secured.

Recommended defensive actions

• Verify the MCP_AUTH_TOKEN configuration and ensure that the /mcp listener is properly secured.
• Upgrade to version 0.3.2 of genieacs-mcp.
• Monitor for suspicious activity on the loopback listener.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The vulnerability is fixed in version 0.3.2 of genieacs-mcp. The npm wrapper is not affected because it forces TRANSPORT=stdio and does not expose an HTTP listener. Evidence is limited to public statements from the vendor and CVE Program record. Defenders should verify the MCP_AUTH_TOKEN configuration and /mcp listener security with the vendor and review CPE management state.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.