Vulnerability in Envoy is a high-performance edge/middle/service proxy. In (CVE-2025-66220)
Summary
Vulnerability in Envoy is a high-performance edge/middle/service proxy. In (CVE-2025-66220). Confidential information can be exposed externally.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-66220 has been found in Envoy is a high-performance edge/middle/service proxy. In.
Confidential information can be exposed externally. CVSS score: 5.0/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Envoy is a high-performance edge/middle/service proxy. In CVE-2025-66220" on the vendor's site.
CVE-2025-66220 (Envoy is a high-performance edge/middle/service proxy. In) — CWE-170 / CVSS v3 5.0
Attack vector: remote (network-reachable) / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-170) exists in Envoy is a high-performance edge/middle/service proxy. In.
Check the vendor advisory for the affected versions of Envoy is a high-performance edge/middle/service proxy. In.
Severity: Medium (CVSS 5.0/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Envoy is a high-performance edge/middle/service proxy. In を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- exploit security-advisories@github.com