Skip to main content
VulnerabilityPublished Updated

CVE-2026-63374: AnyIO · TLSStream IDNA 2003 host name encoding enables potential TLS certificate spoofing

Affects mcp-proxySource GCVE Database

0
Compare
Authoritative record:CVE-2026-63374· Critical 9.3

Not known to be exploited · CVSS 9.3 Critical : upgrade to 0.12.0_4 as a priority.

Data as of 4 Nov 2026, 07:12 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.12.0_4
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.

What to do

Upgrade mcp-proxy to 0.12.0_4.

Affected software

ProductAffectedFixed in
Homebrewmcp-proxypkg:brew/mcp-proxyOther threatsAffected
  • >=0.8.2 <0.12.0_4
Fixed in
  • 0.12.0_4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in AnyIO version 0.12.0_4 that fixes this vulnerability. Users should upgrade to this version to remediate the issue. As a temporary workaround, host names should be encoded using the 'idna' package prior to connecting to avoid the vulnerable IDNA 2003 encoding.

Description

AnyIO's TLSStream uses IDNA 2003 encoding for internationalized domain names, which can enable TLS certificate spoofing. An attacker who hijacks and redirects a TLS connection to a malicious server can obtain a legitimate certificate for the IDNA 2003 encoded domain and present it to the client, causing the client to accept the spoofed certificate. This vulnerability affects versions from 0.8.2 up to but not including 0.12.0_4. A fix is available in version 0.12.0_4. As a workaround, host names can be encoded using the 'idna' package before connecting.

References

Community reviews

Loading reviews…