Skip to content
IoT

CVE-2026-55637

8.8
High
EPSS 0.21%Patch availableAug 26, 2026

DNS rebinding lets web pages control GenieACS via unauthenticated MCP listener.

common questions

Is CVE-2026-55637 being exploited?

Not confirmed. CVE-2026-55637 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.21% probability of exploitation in the next 30 days.

How severe is CVE-2026-55637?

CVE-2026-55637 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-55637?

Yes. A fix has been recorded for CVE-2026-55637. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-55637 affect?

CVE-2026-55637 affects genieacs-mcp <0.3.2, GenieACS NBI, CPE devices managed by GenieACS, Default MCP listener 127.0.0.1:8080. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-55637?

Upgrade to genieacs-mcp 0.3.2, set MCP_AUTH_TOKEN, restrict MCP_LISTEN_ADDR, validate Host/Origin

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
genieacs-mcp <0.3.2GenieACS NBICPE devices managed by GenieACSDefault MCP listener 127.0.0.1:8080
impact

DNS rebinding to unauthenticated MCP HTTP listener allows remote attackers to invoke GenieACS NBI: reboot devices, push firmware, change TR-069 params, provision or run tasks.

action required

Immediate action required

affected versions
GeiserX genieacs-mcp
  • affected< 0.3.2

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free