{"id":"CVE-2026-5430","aliases":["EUVD-2026-53822","GHSA-j7vh-5w8q-4m4x"],"status":"published","title":"Authentication Bypass via JWT Algorithm Mismatch in Multiple WSO2 Products Allows Account Takeover","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.\n\nSuccessful 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.","severity":{"version":"3.1","score":10,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","level":"critical","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-10","score":0.2239,"percentile":0.97714,"model":"v2026.06.15"},"facts":{"in_kev":true,"known_exploited":true,"public_exploit":true,"fix_available":false},"cwes":["CWE-347"],"published":"2026-08-06T07:33:28Z","modified":"2026-09-25T12:53:05Z","kev":{"date_added":"2026-09-24","due_date":"2026-09-27","required_action":"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.","known_ransomware_use":"Unknown"},"exploitation":[{"source":"euvd","since":"2026-09-24"},{"source":"kev","since":"2026-09-24"}],"exploits":[{"source":"pocgithub","id":"HORKimhab/CVE-2026-5430","title":"HORKimhab/CVE-2026-5430","date":"2026-09-16","url":"https://github.com/HORKimhab/CVE-2026-5430"},{"source":"pocgithub","id":"abraxas/CVE-2026-5430","title":"abraxas/CVE-2026-5430","date":"2026-09-25","url":"https://github.com/abraxas/CVE-2026-5430"},{"source":"pocgithub","id":"davidvrns/CVE-2026-5430-WSO2","title":"davidvrns/CVE-2026-5430-WSO2","date":"2026-10-08","url":"https://github.com/davidvrns/CVE-2026-5430-WSO2"},{"source":"pocgithub","id":"getdrive/wso2_cve-2026-5430_lab","title":"getdrive/wso2_cve-2026-5430_lab","date":"2026-10-08","url":"https://github.com/getdrive/wso2_cve-2026-5430_lab"}],"products":[{"vendor":"wso2","product":"api_control_plane"},{"vendor":"wso2","product":"api_manager"},{"vendor":"wso2","product":"multiple products"},{"vendor":"wso2","product":"traffic_manager"},{"vendor":"wso2","product":"universal_gateway"},{"vendor":"wso2","product":"wso2 api control plane"},{"vendor":"wso2","product":"wso2 api manager"},{"vendor":"wso2","product":"wso2 carbon api manager rest api utility"},{"vendor":"wso2","product":"wso2 traffic manager"},{"vendor":"wso2","product":"wso2 universal gateway"}],"references":[{"url":"https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2026-5328/","tags":["vendor-advisory","Vendor Advisory"]},{"url":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-5430","tags":["government-resource","US Government Resource"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-5430"},{"url":"https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2026-5328"},{"url":"https://github.com/advisories/GHSA-j7vh-5w8q-4m4x"}],"sources":{"cve":[{"id":"CVE-2026-5430","title":"Authentication Bypass via JWT Algorithm Mismatch in Multiple WSO2 Products Allows Account Takeover","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.\n\nSuccessful 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.","status":"published","published":"2026-08-06T07:33:28.156Z","modified":"2026-09-25T03:55:16.285Z","cvss":[{"version":"3.1","score":10,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","level":"critical","assessor":"cna"}],"cwes":["CWE-347"],"updated_at":"2026-11-02T13:39:27.849196Z"}],"euvd":[{"id":"EUVD-2026-53822","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.\n\nSuccessful 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.","status":"published","published":"2026-08-06T07:33:28Z","modified":"2026-09-25T03:55:16Z","cvss":[{"version":"3.1","score":10,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","level":"critical"}],"exploited_since":"2026-09-24","updated_at":"2026-11-02T17:27:55.846756Z"}],"ghsa":[{"id":"GHSA-j7vh-5w8q-4m4x","title":"The JWT authentication mechanism accepts tokens signed with algorithms other than those...","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.\n\nSuccessful 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.","status":"published","published":"2026-08-06T09:30:32Z","modified":"2026-09-24T21:32:26Z","cvss":[{"version":"3.1","score":10,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","level":"critical"}],"cwes":["CWE-347"],"updated_at":"2026-11-02T15:12:23.588673Z"}],"kev":[{"id":"CVE-2026-5430","title":"WSO2 Multiple Products Path Traversal Vulnerability ","description":"WSO2 API Control Plane, API Manager, Traffic Manager \u0026 Universal Gateway contain a path traversal vulnerability that could allow for unrestricted file upload and lead to remote code execution. ","cwes":["CWE-347"],"kev":{"date_added":"2026-09-24","due_date":"2026-09-27","required_action":"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.","known_ransomware_use":"Unknown"},"updated_at":"2026-11-02T17:00:15.999436Z"}],"nvd":[{"id":"CVE-2026-5430","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.\n\nSuccessful 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.","status":"published","published":"2026-08-06T08:16:33.24Z","modified":"2026-09-25T12:53:05.517Z","cvss":[{"version":"3.1","score":10,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","level":"critical","assessor":"secondary"}],"cwes":["CWE-347"],"updated_at":"2026-11-02T14:12:35.031043Z"}]}}