CVE-2026-87830
validatedZero produced an exploit or a check.GHSA-66vg-36xv-j6x4 ↗EUVD-2026-89792 ↗
description
Apache WSS4J's StAX streaming WS-SecurityPolicy validator can mishandle certain relative or unsupported XPath expressions. A remote SOAP peer may cause a required XML element to be accepted without the policy's expected signature or encryption when affected XPath-based policy rules are used.
mitigation
Upgrade org.apache.wss4j:wss4j-ws-security-policy-stax to 4.0.2, 3.0.6, or 2.4.4, as appropriate for your release line.
fixed in 4.0.2, 3.0.6, 2.4.4
outcome
Mechanism verified: the exploit fired on the vulnerable build and stayed silent on the patched one, but the server it ran against was ours, so no check ships for it.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-09-30 11:57Zcve_org: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/CVE-2026-87830
{ "etk_id": "ETK-2026-513", "cve_id": "CVE-2026-87830", "display_id": "CVE-2026-87830", "ghsa_id": "GHSA-66vg-36xv-j6x4", "euvd_id": "EUVD-2026-89792", "status": "published", "anchor_state": "anchored", "title": "WS-SecurityPolicy XPath validation bypass in Apache WSS4J", "summary": "Apache WSS4J's StAX streaming WS-SecurityPolicy validator can mishandle certain relative or unsupported XPath expressions. A remote SOAP peer may cause a required XML element to be accepted without the policy's expected signature or encryption when affected XPath-based policy rules are used.", "mitigation": "Upgrade org.apache.wss4j:wss4j-ws-security-policy-stax to 4.0.2, 3.0.6, or 2.4.4, as appropriate for your release line.", "vendor": "Apache Software Foundation", "product": "Apache WSS4J", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 4.0.0, < 4.0.2", ">= 3.0.0, < 3.0.6", ">= 0, < 2.4.4" ], "ecosystem": null, "fixed_versions": [ "4.0.2", "3.0.6", "2.4.4" ], "package_name": "org.apache.wss4j:wss4j-ws-security-policy-stax", "purl": null } ], "cwes": [ 917 ], "cvss_score": 9.1, "cvss_src": "nvd", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N", "epss_score": 0.0021, "epss_percentile": 0.1095, "epss_asof": "2026-10-20", "automation": "contextual", "check": true, "check_confidence_basis": "mechanism_verified", "exploit": false, "pipeline_minutes": 20.01464145, "t0_at": "2026-09-30T11:57:01.017000+00:00", "signals": { "check": { "at": "2026-10-04T00:02:16.541414+00:00", "days": 3.503651902939815, "is_lower_bound": false, "measured_at": "2026-09-30T11:57:01.017000+00:00", "url": null }, "trigger_signal": { "at": "2026-09-30T11:57:01.017000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-09-30T11:57:01.017000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-87830" } } }
published 2026-10-03 23:42Z
last change 2026-10-21 04:45Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.