{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-87830 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-87830 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-87830 is a critical vulnerability in Apache WSS4J, published on 30 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-87830 and fix it if it is affected.\n\nWhat it is: CVE-2026-87830 is a critical vulnerability in Apache WSS4J, published on 30 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-87830 in the wild and no public exploit code.\n\nAffected product: Apache WSS4J. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-87830/ (Markdown: https://insights.sbomify.com/CVE-2026-87830/index.md)","id":"CVE-2026-87830","markdown":"https://insights.sbomify.com/CVE-2026-87830/index.md","name":"CVE-2026-87830","record":{"aliases":["DEBIAN-CVE-2026-87830","GHSA-66vg-36xv-j6x4","UBUNTU-CVE-2026-87830"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Java WS-Security library","requires_auth":"none","summary":"Remote attackers can bypass WS-SecurityPolicy signature and encryption checks on SOAP elements due to flawed XPath validation in Apache WSS4J.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"wss4j","vendor":"apache"}],"cvss":{"score":9.1,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-917","name":"Improper Neutralization of Special Elements used in an Expression Language Statement"}],"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.\nUsers are recommended to upgrade to versions 4.0.2 or 3.0.6 or 2.4.4, which fix this issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Apache WSS4J: Streaming WS-SecurityPolicy validation may skip element-protection checks.","id":"CVE-2026-87830","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Checkout Field Manager \u003c 7.9.7 - Subscriber+ Arbitrary Attachment Deletion via Customer Address Custom Field","id":"CVE-2026-87831"},"packages":[],"prev":{"headline":"Checkout Field Manager \u003c 7.9.7 - Subscriber+ Arbitrary Attachment Deletion via Unvalidated Attachment ID Reparenting","id":"CVE-2026-87829"},"products":["Apache WSS4J"],"published":"2026-09-30","related":[{"cvss_score":9.8,"headline":"Apache WSS4J: SAML Sender-Vouches Authentication Bypass","id":"CVE-2026-88920","kev_date_added":null,"published":"2026-09-30"},{"cvss_score":9.1,"headline":"Apache WSS4J: WSS4J EncryptedHeader child confusion causing wrong protected-header selection","id":"CVE-2026-89238","kev_date_added":null,"published":"2026-09-30"},{"cvss_score":7.5,"headline":"Apache WSS4J: Insufficient Validation of Derived-Key Parameters","id":"CVE-2026-85532","kev_date_added":null,"published":"2026-09-30"},{"cvss_score":7.5,"headline":"Apache WSS4J: WS-SecurityPolicy signature checks skipped in the streaming code after an STR-Transform reference","id":"CVE-2026-92121","kev_date_added":null,"published":"2026-09-30"},{"cvss_score":7.5,"headline":"Apache WSS4J: Unauthenticated denial of service via integer overflow in DER parsing of X.509 certificate extensions","id":"CVE-2026-95616","kev_date_added":null,"published":"2026-09-30"},{"cvss_score":7.5,"headline":"Use of a Broken or Risky Cryptographic Algorithm in Apache WSS4J","id":"CVE-2015-0226","kev_date_added":null,"published":"2017-10-30"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-30","vendors":["Apache Software Foundation"]},"summary":"Remote attackers can bypass WS-SecurityPolicy signature and encryption checks on SOAP elements due to flawed XPath validation in Apache WSS4J.","url":"https://insights.sbomify.com/CVE-2026-87830/"}