Skip to main content
VulnerabilityPublished Updated

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

Affects cycodeSource GCVE Database

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

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

Data as of 10 Nov 2026, 19:02 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 3.26.0
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 10 Nov 2026.

What to do

Upgrade cycode to 3.26.0.

Affected software

ProductAffectedFixed in
Homebrewcycodepkg:brew/cycodeOther threatsAffected
  • >=3.2.0 <3.26.0
Fixed in
  • 3.26.0

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 3.26.0 that fixes this vulnerability. Users should upgrade to version 3.26.0 or later. As a temporary workaround, host names can be encoded using the 'idna' package before connecting to avoid the vulnerable IDNA 2003 encoding behavior.

Description

AnyIO versions from 3.2.0 up to but not including 3.26.0 are vulnerable to a TLS certificate spoofing issue involving IDNA 2003 host name encoding. This vulnerability allows an attacker who hijacks and redirects a TLS connection to a malicious server to present a legitimate certificate encoded with IDNA 2003, which validates correctly on the client side. The issue is patched in version 3.26.0. As a workaround, host names can be encoded using the 'idna' package before connecting.

References

Community reviews

Loading reviews…