CVE-2026-63374: AnyIO · TLSStream IDNA 2003 host name encoding enables potential TLS certificate spoofing
Affects glancesSource GCVE Database
Not known to be exploited · CVSS 9.3 Critical : upgrade to 4.5.5_1 as a priority.
Data as of 9 Nov 2026, 19:48 UTC
- Patch
- Available – fixed in 4.5.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:NExploitation evidence
Disclosed: evidence found.
CVE published 22 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 9 Nov 2026.
What to do
Upgrade glances to 4.5.5_1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewglancespkg:brew/glancesOther threats | Affected
| Fixed in
|
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 4.5.5_1. Users should upgrade to this version to remediate the issue. As a workaround, host names can be encoded using the 'idna' package before establishing TLS connections. No other actions are specifically required according to the vendor advisory.
Description
AnyIO versions from 4.2.1 up to but not including 4.5.5_1 have a vulnerability in TLSStream related to IDNA 2003 host name encoding. This flaw allows an attacker who has hijacked and redirected a TLS connection using internationalized domain names to present a malicious server certificate encoded with IDNA 2003, which the client may accept as valid. The vulnerability is critical with a CVSS 4.0 score of 9.3. A patch is available in version 4.5.5_1, and a workaround involves manually encoding host names using the 'idna' package before connecting.
References
- github.com/agronholm/anyio/security/advisories/GHSA-82r6-8w77-94w6 (opens in a new tab)
- github.com/agronholm/anyio/pull/1208 (opens in a new tab)
- github.com/agronholm/anyio/commit/68f58915f82d9be8109ebbbd8f5d70577d43f2ce (opens in a new tab)
- github.com/agronholm/anyio (opens in a new tab)
- github.com/agronholm/anyio/releases/tag/4.14.2 (opens in a new tab)