Skip to main content
VulnerabilityPublished Updated

CVE-2026-0637: WSO2 API Manager · Improper Input Validation

Affects WSO2 API ManagerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.4 Medium · fixed in 4.6.0.12 : update WSO2 API Manager when convenient.

Data as of 5 Nov 2026, 11:40 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (WSO2)CVSS 3.15.4
EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.6.0.12, 4.5.0.44, 4.4.0.63 +7
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
WSO2WSO2 API ManagerAffected
  • >=4.6.0 <4.6.0.12
Fixed in
  • 4.6.0.12
WSO2WSO2 API ManagerAffected
  • >=4.5.0 <4.5.0.44
Fixed in
  • 4.5.0.44
WSO2WSO2 API ManagerAffected
  • >=4.4.0 <4.4.0.63
Fixed in
  • 4.4.0.63
WSO2WSO2 API ManagerAffected
  • >=4.3.0 <4.3.0.99
Fixed in
  • 4.3.0.99
WSO2WSO2 API ManagerAffected
  • >=4.2.0 <4.2.0.189
Fixed in
  • 4.2.0.189
WSO2WSO2 API ManagerAffected
  • >=4.1.0 <4.1.0.249
Fixed in
  • 4.1.0.249

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, administrators should carefully review and restrict configurations of Event Publisher output adapters to avoid logging sensitive information. Access to 'wso2carbon' log files should be tightly controlled to prevent unauthorized reading.

Description

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.

References

Community reviews

Loading reviews…