https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-06T20:27:50.952680+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bit-envoy-2025-66220 BIT-envoy-2025-66220 — Envoy’s TLS certificate matcher for `match_typed_subject_alt_names` may incorrectly treat certificates containing an em… 2026-10-06T20:27:50.987635+00:00

Affected: Bitnami: envoy

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.

 https://cve.radiocsirt.org/vuln/euvd-2026-262453 EUVD-2026-262453 2026-10-06T20:27:50.987733+00:00 EUVD-2026-262453 https://cve.radiocsirt.org/vuln/fkie_cve-2025-66220 fkie_cve-2025-66220 2026-10-06T20:27:50.987750+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-rwjg-c3h2-f57p GHSA-rwjg-c3h2-f57p — Envoy's TLS certificate matcher for `match_typed_subject_alt_names` may incorrectly treat certificates containing an em… 2026-10-06T20:27:50.987775+00:00

Affected: Go: github.com/envoyproxy/envoy

### 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 [markevich.nikita1@gmail.com](mailto:markevich.nikita1@gmail.com)