CVE-2025-0752 json
Envoyproxy: openshift service mesh envoy http header sanitization bypass leading to dos and unauthorized access
published 2025-01-28 21 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-1853
- cvss
- 7.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 36%
- public exploits
- 0
- none known
Summary
A flaw was found in OpenShift Service Mesh 2.6.3 and 2.5.6. Rate-limiter avoidance, access-control bypass, CPU and memory exhaustion, and replay attacks may be possible due to improper HTTP header sanitization in Envoy.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-0752 updated cvss 7.1
envoyproxy: OpenShift Service Mesh Envoy HTTP Header Sanitization Bypass Leading to DoS and Unauthorized Access
-
Red Hat OpenShift Service Mesh 2 openshift-service-mesh/proxyv2-rhel8affected: workaround, no fix available
-
Red Hat OpenShift Service Mesh 2 openshift-service-mesh/proxyv2-rhel9not affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 21 mo ago
Exploit prediction
0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H |
Affected products
- Red Hat OpenShift Service Mesh 2
Classification
- Weakness
-
- CWE-444 Inconsistent Interpretation of HTTP Requests
References
-
access.redhat.com
/security/cve/CVE-2025-0752
vdb-entry, vendor-advisory
-
bugzilla.redhat.com
/show_bug.cgi?id=2339115
issue-tracking, vendor-advisory
Sources
- CVE List CVE-2025-0752
- NVD CVE-2025-0752
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.