Skip to main content
VulnerabilityPublished Updated

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

Affects datasetteSource GCVE Database

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

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

Data as of 18 Nov 2026, 18:33 UTC

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

What to do

Upgrade datasette to 0.65.2_6.

Affected software

ProductAffectedFixed in
Homebrewdatasettepkg:brew/datasetteOther threatsAffected
  • >=0.58 <0.65.2_6
Fixed in
  • 0.65.2_6

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.65.2_6 that fixes this vulnerability. Users should upgrade to this version to remediate the issue. As a workaround, hostnames can be encoded using the 'idna' package before making TLS connections. No other actions are specifically required according to the advisory.

Description

AnyIO versions from 0.58 up to but not including 0.65.2_6 have a vulnerability in TLSStream where the use of IDNA 2003 host name encoding can enable TLS certificate spoofing. This affects services using internationalized domain names (non-ASCII). An attacker who hijacks and redirects a TLS connection can present a legitimate certificate encoded with IDNA 2003, causing the client to accept a spoofed certificate. The issue is patched in version 0.65.2_6. A workaround is to encode host names using the 'idna' package before connecting.

References

Community reviews

Loading reviews…