CVE-2025-66220: Envoy's TLS certificate matcher for `match_typed_subject_alt_names` may incorrectly treat certificates containing an embedded null byte
Summary Envoy’s mTLS certificate matcher for matchtypedsubjectaltnames may incorrectly treat certificates containing an embedded null byte (\0) inside an OTHERNAME SAN value as valid matches. Details This occurs when the SAN is encoded as a BMPSTRING or UNIVERSALSTRING, and its UTF-8 conversion result is truncated at the first null byte during string assignment.
Published Dec 5, 2025
Affected packages
github.com/envoyproxy/envoy
- Ecosystem
- Go
- Affected
- >= 1.36.0, <= 1.36.2
- Fixed in
- 1.36.3
- Check
go list -m github.com/envoyproxy/envoy
github.com/envoyproxy/envoy
- Ecosystem
- Go
- Affected
- >= 1.35.0, <= 1.35.6
- Fixed in
- 1.35.7
- Check
go list -m github.com/envoyproxy/envoy
github.com/envoyproxy/envoy
- Ecosystem
- Go
- Affected
- >= 1.34.0, <= 1.34.10
- Fixed in
- 1.34.11
- Check
go list -m github.com/envoyproxy/envoy
github.com/envoyproxy/envoy
- Ecosystem
- Go
- Affected
- <= 1.33.12
- Fixed in
- 1.33.13
- Check
go list -m github.com/envoyproxy/envoy
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
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.
Details
This occurs when the SAN is encoded as a BMPSTRING or UNIVERSALSTRING, and its UTF-8 conversion result is truncated at the first null byte during string assignment. As a result, "victim\0evil" may match an exact: "victim" rule and be accepted by Envoy.
PoC
Create a CA and a server certificate signed by that CA. Create two client certificates signed by the same CA: client_evil with OTHERNAME BMPSTRING = "evil" client_null with OTHERNAME BMPSTRING = "victim\0evil" Configure Envoy with require_client_certificate: true and a match_typed_subject_alt_names entry for the OTHERNAME OID with matcher.exact: "victim". Connect without a client cert → connection rejected. Connect with client_evil → connection rejected. Connect with client_null → connection accepted (but shouldn't!).
Impact
An attacker who can obtain a trusted client certificate with a null byte embedded in an OTHERNAME SAN can exploit this vulnerability. The practical impact is unauthorized impersonation of the matched identity, enabling access to services or APIs protected by that exact OTHERNAME check.
Credit
[[email protected]](mailto:[email protected])
Credited to botengyao, phlax, ggreenway, yanavlasov, agrawroh.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-26308
Envoy has RBAC Header Validation Bypass via Multi-Value Header Concatenation
high7.5Mar 10, 2026CVE-2026-26309
Envoy affected by off-by-one write in JsonEscaper::escapeString()
medium5.3No fixMar 10, 2026CVE-2026-26310
Envoy vulnerable to crash for scoped ip address during DNS
medium5.9No fixMar 10, 2026CVE-2026-26311
Envoy: HTTP - filter chain execution on reset streams causing UAF crash
medium5.9No fixMar 10, 2026CVE-2026-26330
Envoy's global rate limit may crash when the response phase limit is enabled and the response phase request is failed directly
medium5.3No fixMar 10, 2026CVE-2025-64527
Envoy crashes when JWT authentication is configured with the remote JWKS fetching
medium6.5Dec 5, 2025
