Helio dashboard CORS origin check matches hostname prefixes
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- None · Low · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-346.
Summary
Helio, an MCP proxy, before 0.8.0 checks CORS origins for its dashboard sideband by matching hostname prefixes such as 192.168. instead of validating IP addresses (CWE-346). Public DNS names like 192.168.attacker.com pass this check, so the proxy echoes the attacker origin in Access-Control-Allow-Origin. A remote attacker without privileges or user interaction can send cross-origin requests to the dashboard and modify its data.
Written with Claude Haiku 5.5 from the sources below · 2026-11-11
Description from the CNA
Helio is an MCP proxy that sits between AI agents and the tools they use. Prior to version 0.8.0, the dashboard sideband (default 127.0.0.1:3100) validated CORS request origins by matching the hostname against a private-network string prefix (10., 172.16.–172.31., 192.168.) rather than validating an IP address. A public DNS name such as 192.168.attacker.com, 10.evil.io, or 172.16.pwn.example also satisfies that prefix, so the proxy echoed the attacker origin in Access-Control-Allow-Origin. This issue has been patched in version 0.8.0.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
Upgrade Helio to version 0.8.0, which fixes this issue.
Written with Claude Haiku 5.5 from the sources below · 2026-11-11
- Fix · CNA helio (gethelio) Fixed in 0.8.0
Timeline
- 2026-11-11 Threatist record created from CVE-2026-65957
- 2026-11-12 CISA SSVC decision points changed
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences