Skip to main content
VulnerabilityPublished Updated

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

Affects certbotSource GCVE Database

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

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

Data as of 13 Nov 2026, 21:31 UTC

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

What to do

Upgrade certbot to 5.7.0.

Affected software

ProductAffectedFixed in
Homebrewcertbotpkg:brew/certbotOther threatsAffected
  • >=5.6.0 <5.7.0
Fixed in
  • 5.7.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 fixing this vulnerability is available in AnyIO version 5.7.0. Users should upgrade to this version to remediate the issue. As a workaround before upgrading, host names should be encoded using the 'idna' package prior to establishing TLS connections. No other actions are indicated by the vendor advisory.

Description

AnyIO versions 5.6.0 up to but not including 5.7.0 contain a vulnerability in TLSStream's handling of internationalized domain names (IDNA 2003 encoding). This flaw allows an attacker who has hijacked and redirected a TLS connection to present a malicious server with a legitimate certificate encoded using the older IDNA 2003 standard. The client would validate this certificate successfully, enabling potential TLS certificate spoofing. A fix is available in version 5.7.0. As a workaround, host names can be encoded using the 'idna' package before connecting.

References

Community reviews

Loading reviews…