CVE-2026-0637
Header Injection via Custom URL Configuration in Multiple WSO2 Products Allows Open Redirect and Log Forgery
When a proxy server is configured with `customUrl.enabled`, the component accepts user-supplied input within forwarded HTTP headers without enforcing expected validation constraints. A malicious actor can manipulate these headers to influence the URL construction process, leading to an open redirect vulnerability. Additionally, unsanitized header values are written to application logs. An attacker can exploit this to force redirection to arbitrary malicious domains, potentially enabling phishing attacks. Furthermore, they can inject forged entries into application logs, impacting the reliability of security logs and potentially hindering incident investigation.
Fixes and workarounds
Fix
Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4829/#solution https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4829/#solution
Source: CNA: WSO2Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| WSO2 API Manager WSO2 |
≥ 0; < 3.2.0 (unknown, custom) ≥ 3.2.0; < 3.2.0.464 (affected, custom) ≥ 3.2.1; < 3.2.1.83 (affected, custom) ≥ 4.1.0; < 4.1.0.249 (affected, custom) ≥ 4.2.0; < 4.2.0.189 (affected, custom) ≥ 4.3.0; < 4.3.0.99 (affected, custom) ≥ 4.4.0; < 4.4.0.63 (affected, custom) ≥ 4.5.0; < 4.5.0.44 (affected, custom) ≥ 4.6.0; < 4.6.0.12 (affected, custom) Other versions: unaffected |
CNA: WSO2 |
| WSO2 API Control Plane WSO2 |
≥ 0; < 4.5.0 (unknown, custom) ≥ 4.5.0; < 4.5.0.45 (affected, custom) ≥ 4.6.0; < 4.6.0.13 (affected, custom) Other versions: unaffected |
CNA: WSO2 |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.1 / 5.4 medium |
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N | CNA: WSO2 |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4829/CNA: WSO2 · vendor-advisory
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.