The short version
- The KEV additions. CISA added CVE-2026-5430 in WSO2 products and CVE-2026-71362 in Adobe Commerce and Magento to its Known Exploited Vulnerabilities (KEV) catalogue, a list of flaws with evidence of active attack. Federal civilian agencies were given until 27 September to apply fixes.
- WSO2 flaw described two ways. One source calls CVE-2026-5430 a path traversal flaw allowing file upload and remote code execution; another calls it an authentication bypass in which the JWT mechanism accepts tokens signed with an unsupported algorithm. Both rate it critical and say it affects WSO2 API Manager, API Control Plane, Traffic Manager and Universal Gateway.
- Adobe Commerce impact. CVE-2026-71362 is an incorrect authorisation flaw in Adobe Commerce and Magento that needs no account, administrator rights or user interaction. According to Sansec, it lets an attacker move a customer session to another customer's account, exposing private data.
- Evidence of attempts. Sansec says it detected and blocked exploitation attempts in August 2026. WatchTowr reported forged-token attempts against WSO2 software on 13 September, initially aimed at the wrong product, and then reproduced the attack.
- Two further flaws named. CISA also cited a high-severity code injection flaw in Microsoft SharePoint, CVE-2026-65660, and a medium-severity pre-authentication bypass in Mikrotik RouterOS, CVE-2026-67279, as exploited, with a 28 September deadline for agencies.
Timeline
| Date | Event |
|---|---|
| 3 May | WSO2 publishes its advisory for CVE-2026-5430, warning that exploitation could let an attacker compromise administrative accounts and take full control. |
| August | Sansec says it detected and blocked exploitation attempts against CVE-2026-71362 in Adobe Commerce and Magento. |
| 10 Sep | Previdian reports a single IP address in Australia attempting to exploit CVE-2026-71362 against its honeypot sensors. |
| 13 Sep | WatchTowr honeypots record a limited number of forged-JWT attempts from one IP address against a WSO2 product, in an attack aimed at the wrong product. |
| 15 Sep | WatchTowr announces the honeypot observations. It also reproduced the attack against the correct WSO2 product. |
| 25 Sep | CISA's addition of both flaws to the KEV catalogue is reported, with a 27 September deadline for federal agencies. |
What CISA added, and what it did not say
CISA added CVE-2026-5430 and CVE-2026-71362 to its Known Exploited Vulnerabilities catalogue on the basis of evidence that both are being used in attacks. Federal civilian agencies had until 27 September to apply updates or stop using the affected products.
The agency has not published details of the attacks it relied on. Adobe has not updated its advisory to confirm that CVE-2026-71362 has been exploited, according to The Hacker News. CISA encourages organisations outside the federal government to prioritise the same fixes.
WSO2: one flaw, two technical descriptions
The sources disagree on what CVE-2026-5430 is. The Hacker News describes it as a path traversal flaw, rated 9.8, that allows unrestricted file upload and can lead to remote code execution. BleepingComputer describes it as an authentication bypass stemming from a JWT (JSON Web Token, a signed token used to prove identity) mechanism that accepts tokens signed with an algorithm it should not support. Both rate the flaw critical.
BleepingComputer reports that the flaw affects WSO2 API Manager versions 4.1.0 through 4.6.0, plus API Control Plane, Traffic Manager and Universal Gateway versions 4.5.0 and 4.6.0. WSO2's advisory of 3 May says successful exploitation could compromise administrative accounts and give an attacker full control.
WatchTowr recorded a limited number of attempts from one IP address on 13 September using forged tokens, but the attacker targeted the wrong WSO2 product. WatchTowr then reproduced the attack on the correct product, where a forged token could expose API endpoints and application credentials. Its threat intelligence specialist, Yordan Ganchev, put WSO2's customer base at nearly 1,000 organisations in banking, government, telecommunications and logistics.
Adobe Commerce: sessions and customer data
CVE-2026-71362 lets an attacker gain elevated access to sensitive resources without user interaction, and Sansec says no existing account or administrator privileges are needed. "The vulnerability lets attackers switch a customer session to another customer account," the company said. That gives access to the victim's account and private customer data.
Sansec detected and blocked exploitation attempts in August 2026, and Previdian saw a single Australian IP address probing its honeypot sensors on 10 September 2026. For WSO2, watchTowr says it has seen exploitation attempts against its honeypots since at least 13 September. The KEV listing reflects CISA's evidence that both flaws are being exploited.
What is not known yet
- Who is carrying out the exploitation attempts, and whether one actor is behind attempts against both products.
- How many organisations have been successfully compromised through either flaw.
- Whether customer data or payment details were taken from any Adobe Commerce or Magento store.
- What specific evidence CISA used to add the two flaws to the KEV catalogue, which the agency has not disclosed.
- Whether the exploit attempts against WSO2 succeeded anywhere, given that watchTowr's first observed attempt used the wrong product.
What to do
If you run WSO2 API Manager, API Control Plane, Traffic Manager or Universal Gateway
- Check your deployed versions against the ranges given: API Manager 4.1.0 to 4.6.0, and Control Plane, Traffic Manager and Universal Gateway 4.5.0 and 4.6.0.
- Apply the fix from WSO2's advisory rather than waiting for confirmation that attacks are succeeding in your sector.
- Review authentication logs for forged or rejected JWT tokens, and check administrative accounts for signs of compromise, since the vendor says exploitation could give full control.
If you run Adobe Commerce or Magento
- Apply the update for CVE-2026-71362, or discontinue use of the affected product.
- Look for customer sessions that change hands between accounts, and treat any that do as a possible compromise of that customer's data.
For everyone else
- Search your estate for all four flaws CISA named this week, including the Microsoft SharePoint code injection flaw CVE-2026-65660 and the Mikrotik RouterOS bypass CVE-2026-67279, and patch them ahead of your normal cycle.
- Treat a KEV listing as a deadline signal rather than background reading, and give internet-facing enterprise software the earliest slot.
Update log
- First published.
Sources
New incident reports by email
One email a week with the reports published since the last one.