# CVE-2025-8154: HTTP Header Injection via Webhook API in Multiple WSO2 Products Allows Response Header Manipulation

> Attackers can inject arbitrary HTTP response headers via the Webhook API, enabling session hijacking and security header manipulation in WSO2 products.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 May 2026
- **Updated:** 11 May 2026
- **Also known as:** GHSA-j72f-vgmh-c8hr

## What is CVE-2025-8154?

CVE-2025-8154 is a medium-severity vulnerability in Wso2 Api Manager, published on 11 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Webhook API invocations, the component accepts user-supplied input for HTTP request headers without sufficient validation or sanitization, allowing these headers to be injected into HTTP responses.

By exploiting this vulnerability, a malicious actor can inject or overwrite arbitrary HTTP response headers. This can lead to various adverse effects, including the manipulation of browser caching, alteration of security-related headers, and the injection of sensitive information such as cookie values, potentially enabling session hijacking or other malicious activities.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

It affects 4 products.


Products: Wso2 Api Control Plane, Wso2 Api Manager, Wso2 Traffic Manager, Wso2 Universal Gateway.

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

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

## Is CVE-2025-8154 being exploited?

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

## Other vulnerabilities in Wso2 Api Manager

- [CVE-2026-5430](https://insights.sbomify.com/CVE-2026-5430/): WSO2 Multiple Products Path Traversal Vulnerability (critical 10.0, exploited in the wild)
- [CVE-2026-1728](https://insights.sbomify.com/CVE-2026-1728/): Privilege Escalation via System REST APIs in Multiple WSO2 Products Permits Admin Account Takeover (critical 9.8)
- [CVE-2025-9312](https://insights.sbomify.com/CVE-2025-9312/): Improper Certificate-Based Authentication Enforcement in Multiple WSO2 Products (critical 9.8)
- [CVE-2025-10611](https://insights.sbomify.com/CVE-2025-10611/): Potential Broken Access Control in Multiple WSO2 Products via System REST APIs (critical 9.8)
- [CVE-2025-9152](https://insights.sbomify.com/CVE-2025-9152/): Improper Privilege Management in Multiple WSO2 API Manager via keymanager-operations DCR Endpoint (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-8154 is a medium-severity vulnerability in Wso2 Api Manager, published on 11 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-8154 in the wild and no public exploit code.

Affected product: Wso2 Api Manager. 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-8154/ (Markdown: https://insights.sbomify.com/CVE-2025-8154/index.md)
```

## Sources

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

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