Skip to main content
VulnerabilityPublished Updated

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

Affects zabbix-cliSource GCVE Database

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

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

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.7.0_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. Weaponised: 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 26 Oct 2026.

What to do

Upgrade zabbix-cli to 3.7.0_1.

Affected software

ProductAffectedFixed in
Homebrewzabbix-clipkg:brew/zabbix-cliOther threatsAffected
  • >=3.0.0 <3.7.0_1
Fixed in
  • 3.7.0_1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

### Impact Services using internationalized (non-ASCII) domain names are potentially vulnerable to TLS connections made from AnyIO's `connect_tcp()` or directly via `TLSStream.wrap()` where the connection has (through other means) been hijacked and redirected to a malicious server. The attacker would obtain a legitimate certificate using the IDNA 2003 encoded version of the domain name and offer it to the connecting client, making the certificate validate properly on the client's end. ### Patches The vulnerability will be patched in v4.14.2. ### Workarounds Encode host names via the `idna` package prior to connecting.

References

Community reviews

Loading reviews…