ApplicationsCritical 9.8Patch available
CVE-2026-88920
Auth bypass in Apache WSS4J allows forging authenticated SAML SOAP messages.
How scary is it?
updated 15 Oct 2026- Yes
Works without logging in1
No account and no user action needed (CVSS PR:N, UI:N).
- Yes
Reachable over the network1
Can be attacked remotely (CVSS AV:N).
- None known
Public exploit code is out
None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
- None known
Attacks seen in the wild1
None reported that we know of. CISA's SSVC assessment says exploitation: none.
- No
On CISA's exploited list2
Not in the catalog as of our last sync.
Scare-o-meter
Act this week
Serious and within reach of attackers. Schedule the fix this week.
- Low signal
- Routine patch
- Act this week
- Drop everything
Why: Reachable over the network with no login and no user action; CVSS 9.8.1 Read from the same rule that decides our alert emails.
Are you affected? only if all are true
You run Apache Software Foundation Apache WSS4J in an affected version>= 4.0.0 and < 4.0.2 / >= 3.0.0 and < 3.0.6 / < 2.4.4
The CVE record states no fixed release.
As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.
See the affected products table · Source 1
An attacker can reach it over the network
CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.
Source 1
Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.
What to do
Per our analysisA patch is available
The CVE record we hold states no fixed release number. See the advisories in the references.
Recommendation, AI-writtenUpgrade WSS4J to 4.0.2 / 3.0.6 / 2.4.4 immediately; review SAML sender-vouches handling.
Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.
Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.
Major vulnerability. WSS4J is a widely used SOAP security library; auth bypass enables forging authenticated SAML SOAP messages across many enterprise apps and middleware.
- CVSS
- 9.8Criticalscored by CISA
- Exploited in the wild
- Not knownnot in CISA KEV as of our last sync
- EPSS
- 0.58%chance of exploitation in the next 30 daystop 52% of scored CVEsFIRST score of 21 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 30 Sept 2026analysed here 1 Oct 2026
Summary
Impact
Unauthenticated attacker can forge authenticated SOAP messages (SAML sender-vouches) to impersonate users, bypass access controls and invoke privileged web service actions.
Triage
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| Apache Software Foundation Apache WSS4J | >= 4.0.0 and < 4.0.2>= 3.0.0 and < 3.0.6< 2.4.4Vendor says fixed in: not stated |
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.
Products named in our analysis
- Apache WSS4J prior to 4.0.2 / 3.0.6 / 2.4.4
- SOAP/SAML-enabled applications using WSS4J
- Middleware and enterprise apps using WSS4J
Fix and mitigation
Action required
Immediate action required
WAF and other mitigations
Can a WAF block it? No. The vulnerability involves forging authenticated SAML SOAP messages, which are typically sent over SOAP protocols rather than standard HTTP requests handled by web servers. Such messages look like normal SOAP traffic, so a web application firewall cannot reliably distinguish malicious from legitimate messages.
Also consider: patch · add auth middleware
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Not listed as of our last sync.
- Public exploit code
- None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
- CISA SSVC
- exploitation none, automatable yes, technical impact totalAssessed by CISA 30 Sept 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
Timeline
- 30 Sept 2026Published
- 30 Sept 2026CISA SSVC assessment: exploitation nonesame day later
- 30 Sept 2026CVE record last updatedsame day later
- 1 Oct 2026Analysed by vulneraibility.comsame day later
Common questions
Is CVE-2026-88920 being exploited?
Not confirmed. CVE-2026-88920 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.58% probability of exploitation in the next 30 days.
How severe is CVE-2026-88920?
CVE-2026-88920 is rated Critical with a CVSS score of 9.8. 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-88920?
Yes. A fix has been recorded for CVE-2026-88920. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-88920 affect?
CVE-2026-88920 affects Apache WSS4J prior to 4.0.2 / 3.0.6 / 2.4.4, SOAP/SAML-enabled applications using WSS4J, Middleware and enterprise apps using WSS4J. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-88920?
Upgrade WSS4J to 4.0.2 / 3.0.6 / 2.4.4 immediately; review SAML sender-vouches handling.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
2 references in the CVE record, grouped by the tags the record gives them.
Advisories (1)
- lists.apache.org /thread.html/grt43m3bgbzz0mk0cnho3rcybb1j01z9
Other links (1)
- openwall.com /lists/oss-security/2026/09/30/10
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.