Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-cmwv-wf9p-p8wx

genieacs-mcp: DNS rebinding reaches local GenieACS MCP Streamable HTTP transport

CVSS 8.8 HighEPSS 0.0026 · 18th percentile

Published by the GitHub Advisory Database at 25 Aug 2026, 18:05 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/geiserx/genieacs-mcpGo<0.3.20.3.2
Identifiers
GHSA-cmwv-wf9p-p8wx · CVE-2026-55637 · GO-2026-6295
Weakness (CWE)
CWE-346
Tags
Published
25 Aug 2026
Updated
26 Aug 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

GenieACS MCP server (github.com/geiserx/genieacs-mcp) versions before 0.3.2 accept attacker-controlled Host and Origin headers on the default loopback Streamable HTTP listener, which requires no authentication token. A malicious web page can use DNS rebinding to reach that listener from a victim's browser, then initialize an MCP session and invoke tools such as device reboot, parameter changes and task management against the configured GenieACS backend. Upgrade to version 0.3.2. Until then, avoid running the HTTP transport on loopback when browsing untrusted sites, or use stdio.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.8 High 4.0 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0026, the 18th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:48 UTC First seen by agentprime
  2. 31 Oct 2026, 14:48 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.