# CVE-2025-0752: Envoyproxy: openshift service mesh envoy http header sanitization bypass leading to dos and unauthorized access

> Attackers can bypass HTTP header sanitization in Envoy to evade rate limiting, bypass access controls, and cause resource exhaustion.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jan 2025
- **Updated:** 24 Feb 2026
- **Also known as:** GHSA-wpxv-x75w-vp46

## What is CVE-2025-0752?

CVE-2025-0752 is a high-severity vulnerability in Red Hat OpenShift Service Mesh 2, published on 28 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests)

## Which versions are affected by CVE-2025-0752?

It affects 1 product.


Products: Redhat Openshift Service Mesh.

## How do I fix CVE-2025-0752?

No fix has been published for CVE-2025-0752 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-0752 being exploited?

There is no known exploitation of CVE-2025-0752 in the wild and no public exploit code.

## Other vulnerabilities in Red Hat OpenShift Service Mesh 2

- [CVE-2021-3586](https://insights.sbomify.com/CVE-2021-3586/): Misconfiguration in servicemesh-operator (critical 9.8)
- [CVE-2020-1704](https://insights.sbomify.com/CVE-2020-1704/): Privilege escalation in openshift-service-mesh/kiali-rhel7-operator (high 7.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-0752 and fix it if it is affected.

What it is: CVE-2025-0752 is a high-severity vulnerability in Red Hat OpenShift Service Mesh 2, published on 28 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0752 in the wild and no public exploit code.

Affected product: Red Hat OpenShift Service Mesh 2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-0752/ (Markdown: https://insights.sbomify.com/CVE-2025-0752/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-0752
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-0752
- OSV: https://osv.dev/vulnerability/CVE-2025-0752

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-0752/
Summaries are generated and may contain mistakes; the official description above is the record.