CVE-2025-66220GHSA-RWJG-C3H2-F57PBIT-ENVOY-2025-66220
Envoy’s TLS certificate matcher for `match_typed_subject_alt_names` may incorrectly treat certificates containing an embedded null byte
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.36.3, 1.35.7, 1.34.11, 1.33.13
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: poc
- Automatable: no
- Technical impact: partial
Summary
Envoy is a high-performance edge/middle/service proxy. In 1.33.12, 1.34.10, 1.35.6, 1.36.2, and earlier, Envoy’s mTLS certificate matcher for match_typed_subject_alt_names may incorrectly treat certificates containing an embedded null byte (\0) inside an OTHERNAME SAN value as valid matches.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- envoyproxy envoy
From 1.36.0 · through 1.36.2; From 1.35.0 · through 1.35.6; From 1.34.0 · through 1.34.10; through 1.33.12
- github.com/envoyproxy/envoyGo
From 1.36.0 · fixed in 1.36.3
- github.com/envoyproxy/envoyGo
From 1.35.0 · fixed in 1.35.7
- github.com/envoyproxy/envoyGo
From 1.34.0 · fixed in 1.34.11
- github.com/envoyproxy/envoyGo
fixed in 1.33.13