Skip to main content
No exploitation reportedFix available

CVE-2026-87830

Apache WSS4J: Streaming WS-SecurityPolicy validation may skip element-protection checks.

No exploitation reported by the sources we read.

  • Published2026-09-30
  • Fixed in4.0.2 · 3.0.6 · 2.4.4
  • WeaknessCWE-917

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

In the StAX streaming WS-SecurityPolicy validator, certain relative or unsupported XPath expressions can be converted into paths that never match the actual XML element path. A remote SOAP peer may therefore send a required element without the expected signature or encryption. Users are recommended to upgrade to versions 4.0.2 or 3.0.6 or 2.4.4, which fix this issue.

Timeline

dates in UTC
  1. 2026-09-3012:17CVE publishedNVD

Versions per branch

NVD
Apache wss4j
BranchAffectedFixed in
4.0≥ 4.0.0, < 4.0.24.0.2
3.0≥ 3.0.0, < 3.0.63.0.6
2.4< 2.4.42.4.4

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As apache, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Apache Software Foundation Apache WSS4Jother versions: not affected

    package org.apache.wss4j:wss4j-ws-security-policy-staxhttps://repo.maven.apache.org/maven2

    Affected
    • ≥ 4.0.0, < 4.0.2fixed in 4.0.2semver
    • ≥ 3.0.0, < 3.0.6fixed in 3.0.6semver
    • < 2.4.4fixed in 2.4.4semver

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-09-30

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • wss4jUbuntu:26.10all versions · no fixed version listed
  • wss4jUbuntu:26.04:LTSall versions · no fixed version listed
  • wss4jUbuntu:24.04:LTSall versions · no fixed version listed
  • wss4jUbuntu:20.04:LTSall versions · no fixed version listed
  • wss4jUbuntu:16.04:LTSall versions · no fixed version listed
  • wss4jDebian:14all versions · no fixed version listed
  • wss4jDebian:13all versions · no fixed version listed

Vendor advisories

  • CVE-2026-87830 Red Hat Product Security3 known affected

    wss4j: Apache WSS4J: Security feature bypass via improper XPath handling in streaming policy validation

    wss4j-ws-security-policy-stax as a component of Red Hat JBoss Enterprise Application Platform 7 · wss4j-ws-security-policy-stax as a component of Red Hat JBoss Enterprise Application Platform 8 · wss4j-ws-security-policy-stax as a component of Red Hat JBoss Enterprise Application Platform Expansion Pack

Full record on NVD

Fix

  1. Update Apache wss4j to 4.0.2 · 3.0.6 · 2.4.4
  2. Workaround from the vendor Red Hat Product Security CVE-2026-87830 · 3 productsMitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
  3. No fix available, says the vendor Red Hat Product Security CVE-2026-87830 · 3 productsFix deferred

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Published
2026-09-30
Last Modified
2026-10-06
NVD status
Analyzed
GitHub Advisory
GHSA-66vg-36xv-j6x4

Frequently asked questions

What is CVE-2026-87830?

In the StAX streaming WS-SecurityPolicy validator, certain relative or unsupported XPath expressions can be converted into paths that never match the actual XML element path. A remote SOAP peer may therefore send a required element without the expected signature or encryption. Users are recommended to upgrade to versions 4.0.2 or 3.0.6 or 2.4.4, which fix this issue.

Is CVE-2026-87830 actively exploited?

Active exploitation of CVE-2026-87830 has not been confirmed. Its EPSS score was 0.2% on 2026-11-16, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-87830?

CVE-2026-87830 has a CVSS v3 base score of 9.1 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N.

Running wss4j? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record