Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-87830: In the StAX streaming WS-SecurityPolicy validator, certain relative or unsupported XPath expressions can be co

45
This month
CRITICAL 9.1REMOTEWATCHLISTUPGRADE

CVE-2026-87830 is a critical-severity flaw (CVSS 9.1) affecting wss4j. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • Critical severity
  • Remotely exploitable, no login, no user action
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score9.1 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.2% (top 88%)
CISA exploited listNo
WeaknessCWE-917
Published2026-09-30
Last modified2026-10-06
Publisher (CNA): Apache Software Foundation · Vendor: apache

Share: LinkedIn · X · Reddit

Last updated 2026-10-06 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

apache wss4j UPGRADE
Affected: < 2.4.4 · >= 3.0.0 and < 3.0.6 · >= 4.0.0 and < 4.0.2
Fixed in: 2.4.4, 3.0.6, 4.0.2
Safe to downgrade to: a release before 3.0.0
1. Check installed version
apt-cache policy wss4j || rpm -q wss4j || wss4j --version
2. UPGRADE to 2.4.4 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade wss4j
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade wss4j
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 3.0.0 (Debian / Ubuntu)
apt-cache madison wss4j sudo apt install wss4j=<VERSION_BEFORE_3.0.0> sudo apt-mark hold wss4j
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list wss4j sudo dnf downgrade wss4j-<VERSION_BEFORE_3.0.0> sudo dnf versionlock add wss4j
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-87830?

wss4j: upgrade to 2.4.4, 3.0.6, 4.0.2. Exact commands for each OS are on this page.

Is CVE-2026-87830 being exploited?

CVE-2026-87830 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-87830 affect?

CVE-2026-87830 affects wss4j. Severity is critical (CVSS 9.1). 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

How urgent is CVE-2026-87830?

Priority 45/100. Critical severity; Remotely exploitable, no login, no user action; On your watchlist

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.