CVE-2026-5430: WSO2 Multiple Products Path Traversal Vulnerability

Compare the exact product, branch, package, platform, and vendor status. An upstream version boundary is not proof that a distribution backport or appliance firmware is vulnerable or fixed.

How the vulnerability works

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. CVE CNA: WSO2

WSO2 Multiple Products may let a crafted path escape its intended directory, exposing configuration, credentials, application data, or a writable execution location.

How to check your systems

Identify the service account and filesystem boundary, review unusual path sequences in logs, patch the canonicalization check, rotate secrets from readable files, and retest encoded traversal variants.

Record the running product build and enabled component from the vendor-supported inventory interface. Compare it with each affected range above, then check the documented authentication and network prerequisites. Keep the output, asset identifier, observation time, and advisory revision with the change ticket.

How to fix

Permanent remediation

Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2026-5328/#solution https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2026-5328/#solution CNA remediation guidance

1. Identify exact product versions, owners, exposure paths, and business-critical dependencies.
2. Apply the latest vendor remediation or isolate the vulnerable path when immediate patching is not possible.
3. Review available telemetry for exploitation attempts before restarting, rebuilding, or rotating evidence away.
4. Validate the fixed version and control health, then record any exception with an owner and expiry date.

Official remediation direction: CISA due date: 2026-09-27. This deadline applies to covered US federal civilian agencies; other organizations should set a risk-based deadline. 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. Official action

If you cannot patch yet

No product-specific workaround is established by the source data available for this article. Ask the vendor for supported options. As an operational precaution, restrict access to the affected interface or isolate the component where service dependencies permit; this is not evidence that the underlying flaw is fixed.

Give any temporary control an owner and expiry, verify it covers every affected instance, and retain a rollback path. Remove it only after the permanent remediation is verified.

Detection and post-fix validation

• Confirm the installed and running version of WSO2 Multiple Products against the current vendor advisory.
• Check whether the vulnerable interface is reachable from untrusted networks or lower-privileged identities.
• Look for new accounts, privilege changes, crashes, child processes, or unusual outbound traffic associated with the component.
• Run a post-remediation service and security-control health check and retain evidence with the change record.

A clean scan or a version match alone does not rule out earlier compromise. If telemetry suggests exploitation, preserve evidence and follow the incident-response process alongside patching.

Timeline and exploitation status

• August 6, 2026 — CVE record published.
• September 24, 2026 — Source entry published.
• September 24, 2026 — Added to CISA KEV.
• September 25, 2026 — Source record updated.

Record publication and KEV addition dates describe those source events; they do not establish when exploitation first began.

The linked official record reports exploitation in the wild. This does not establish that any particular deployment has been compromised.

Public proof-of-concept availability is not independently established here. Recheck the vendor and government records as evidence changes.

Primary sources and references

• CNA-linked reference: security.docs.wso2.com
• CISA-linked vendor guidance: www.cisa.gov
• CISA-linked vendor guidance: www.cisa.gov
• CISA-linked vendor guidance: nvd.nist.gov
• CVE CNA: WSO2: CVE-2026-5430 CNA record
• CISA Known Exploited Vulnerabilities: CVE-2026-5430: WSO2 Multiple Products Path Traversal Vulnerability