Affects a widely-used enterprise API management product; could disrupt internal access and operations.
CVE-2026-2053
Unauth attacker can manipulate WS-Addressing headers to control server-initiated requests.
Is CVE-2026-2053 being exploited?
Not confirmed. CVE-2026-2053 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.39% probability of exploitation in the next 30 days.
How severe is CVE-2026-2053?
CVE-2026-2053 is rated High with a CVSS score of 8.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-2053?
Yes. A fix has been recorded for CVE-2026-2053. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-2053 affect?
CVE-2026-2053 affects WSO2 API Manager. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-2053?
Patch when released; validate WS-Addressing headers and restrict destinations.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated control of destinations for server-initiated requests may access internal resources.
Patch when possible
- affected< 3.1.0
- affected>= 3.1.0 and < 3.1.0.360
- affected>= 3.2.0 and < 3.2.0.465
- affected>= 3.2.1 and < 3.2.1.84
- affected>= 4.0.0 and < 4.0.0.385
- affected>= 4.2.0 and < 4.2.0.189
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.