Wss4j vulnerabilitiesRanked by how likely they are to be used.

Product61 versions
The short answer

Wss4j is made by Apache. We track 5 published vulnerabilities in it, across 61 versions. None of them is on the list of flaws known to be exploited today. If you run Wss4j, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Wss4j vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Wss4j's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Wss4j flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 23%

    An attacker that is able to modify Velocity templates may execute arbitrary Java code or run arbitrary system commands with the same privileges as the account running the Servlet container.

    CVSS8.8Published10 Mar 2021
  2. 9.2%

    Apache WSS4J before 1.6.17 and 2.x before 2.0.2, as used in Apache CXF 2.7.x before 2.7.13 and 3.0.x before 3.0.2, when using TransportBinding, does not properly enforce the SAML SubjectConfirmation method security...

    CVSS5.0Published30 Oct 2014
  3. 7.5%

    Apache WSS4J before 1.6.17 and 2.x before 2.0.2 allows remote attackers to bypass the requireSignedEncryptedDataElements configuration via a vectors related to "wrapping attacks."

    CVSS5.0Published12 Feb 2015
  4. 5.5%

    Apache WSS4J before 1.6.17 and 2.0.x before 2.0.2 improperly leaks information about decryption failures when decrypting an encrypted key or message data, which makes it easier for remote attackers to recover the...

    CVSS7.5Published30 Oct 2017
  5. 1.8%

    The implementations of PKCS#1 v1.5 key transport mechanism for XMLEncryption in JBossWS and Apache WSS4J before 1.6.5 is susceptible to a Bleichenbacher attack.

    CVSS5.9Published11 Mar 2020
  6. 0.5%

    In the WSS4J streaming (StAX) code, a signature reference using the WS-Security STR-Transform leaves an internal "inside signed content" flag permanently set.

    CVSS7.5Published30 Sep 2026
  7. 0.4%

    An integer overflow in WSS4J's DER bounds check lets an oversized allocation pass validation.

    CVSS7.5Published30 Sep 2026
  8. 0.3%

    WSS4J EncryptedHeader child confusion could promote an attacker-controlled plaintext element as the decrypted header, leading to incorrect confidentiality coverage and possible policy bypass.

    CVSS9.1Published30 Sep 2026
  9. 0.2%

    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.

    CVSS9.1Published30 Sep 2026
Precursor Intelligence

Running Wss4j? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 5 published vulnerabilities listed under the name Wss4j, across 61 versions.

None of Wss4j's vulnerabilities is on the list of flaws known to be exploited today.

Create a Precursor Intelligence account and track Wss4j. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.