Skip to main content
VulnerabilityPublished Updated

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

Affects specifySource GCVE Database

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

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

Data as of 5 Nov 2026, 20:05 UTC

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

What to do

Upgrade specify to 0.5.1.

Affected software

ProductAffectedFixed in
Homebrewspecifypkg:brew/specifyOther threatsAffected
  • >=0.0.16 <0.5.1
Fixed in
  • 0.5.1

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.5.1 that fixes this vulnerability. Users should upgrade to version 0.5.1 or later. As a workaround until the patch is applied, host names should be encoded using the 'idna' package before establishing TLS connections. No other actions are specifically recommended.

Description

AnyIO versions from 0.0.16 up to but not including 0.5.1 use IDNA 2003 host name encoding in TLSStream, which can enable TLS certificate spoofing. An attacker who hijacks and redirects a TLS connection to a malicious server can present a legitimate certificate encoded with IDNA 2003, causing the client to validate it incorrectly. This vulnerability is critical and has a CVSS score of 9.3. The issue is fixed in version 0.5.1. As a workaround, host names can be encoded using the 'idna' package before connecting.

References

Community reviews

Loading reviews…