NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Go

CVE-2025-66220: Envoy's TLS certificate matcher for `match_typed_subject_alt_names` may incorrectly treat certificates containing an embedded null byte

mediumCVSS 3.1 5.0GHSA-rwjg-c3h2-f57p

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 entries