# CVE-2025-0754: Envoyproxy: openshift service mesh 2.6.3 and 2.5.6 envoy header handling allows log injection and potential spoofing

> Attackers can inject malicious payloads into service mesh logs via unsanitized headers, enabling log spoofing and reflected XSS attacks.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **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:** 20 Nov 2025
- **Also known as:** GHSA-jwh7-xm52-qvh7

## What is CVE-2025-0754?

CVE-2025-0754 is a medium-severity cross-site scripting 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

The vulnerability was found in OpenShift Service Mesh 2.6.3 and 2.5.6. This issue occurs due to improper sanitization of HTTP headers by Envoy, particularly the x-forwarded-for header. This lack of sanitization can allow attackers to inject malicious payloads into service mesh logs, leading to log injection and spoofing attacks. Such injections can mislead logging mechanisms, enabling attackers to manipulate log entries or execute reflected cross-site scripting (XSS) attacks.

Weakness: CWE-117 (Improper Output Neutralization for Logs)

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


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

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

## Is CVE-2025-0754 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0754 is a medium-severity cross-site scripting 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-0754 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-0754/ (Markdown: https://insights.sbomify.com/CVE-2025-0754/index.md)
```

## Sources

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

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