Skip to main content
VulnerabilityPublished Updated

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

Affects otterdogSource GCVE Database

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

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

Data as of 13 Nov 2026, 21:46 UTC

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

What to do

Upgrade otterdog to 1.3.4_1.

Affected software

ProductAffectedFixed in
Homebrewotterdogpkg:brew/otterdogOther threatsAffected
  • >=1.0.1 <1.3.4_1
Fixed in
  • 1.3.4_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 1.3.4_1 that fixes the IDNA 2003 encoding issue. Users should upgrade to this version to remediate the vulnerability. As a workaround, host names can be encoded using the 'idna' package before establishing TLS connections to avoid the vulnerable encoding method.

Description

AnyIO versions from 1.0.1 up to but not including 1.3.4_1 have a vulnerability in TLSStream related to IDNA 2003 host name encoding. This flaw allows an attacker who hijacks and redirects a TLS connection for internationalized domain names to present a legitimate certificate encoded with IDNA 2003, causing the client to validate the malicious certificate improperly. The issue is patched in version 1.3.4_1. Users can mitigate by pre-encoding host names using the 'idna' package before connecting.

References

Community reviews

Loading reviews…