WSO2 products: file access flaw under attack

What is affected

WSO2 products are found on ordinary personal computers and phones, so this is not only a problem for companies. If you use them and have not updated since the fix was released, you are exposed.

WSO2 API Control Plane, API Manager, Traffic Manager & Universal Gateway contain a path traversal vulnerability that could allow for unrestricted file upload and lead to remote code execution.

What an attacker can do

This is a file access flaw. It lets an attacker read or write files they should never reach, such as configuration files that hold passwords, or upload a malicious file that the system then runs.

How it is reached

Over the internet or network

Access the attacker needs

No account needed

Does the victim have to do something?

No, works without the victim doing anything

What to do

1. Update WSO2 products now. Open the update or "About" screen, install whatever is offered and restart the app or device, because the fix is not active until you do.
2. Turn on automatic updates so the next fix arrives without you having to look for it.
3. If your device is too old to receive this update, stop using the affected app for anything sensitive and plan a replacement.

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Vendor advisories and fixes

• security.docs.wso2.comsecurity.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2026

How urgent is it

CISA added this vulnerability to its Known Exploited Vulnerabilities catalogue on September 24, 2026, which means there is reliable evidence of attacks in the wild. US federal agencies must fix it by September 27, 2026, a deadline that has already passed. That deadline does not bind anyone else, but it shows how seriously the agency rates it.

The EPSS model estimates a 0.6% probability that this flaw will be exploited somewhere in the next 30 days. That is higher than 46% of all scored vulnerabilities.

Its CVSS severity score is 10.0 out of 10 (critical), as recorded in the US National Vulnerability Database.

Technical description

The JWT authentication mechanism accepts tokens signed with algorithms other than those explicitly configured or supported. This allows an attacker to craft a JWT with an unsupported algorithm, which is then incorrectly validated, leading to unauthorized access. Successful exploitation of this vulnerability may result in unauthorized access to the system, including the potential compromise of administrative accounts and full account takeover. The CVSS score is adjusted to 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) in single-tenant deployments, reflecting that the impact is contained within a single security authority boundary.