Advisory record · GHSA-vjwc-5hfh-2vv5

Use of a Broken or Risky Cryptographic Algorithm in Apache WSS4J

CVSS 7.5 HighEPSS 0.055 · 92nd percentile

Published by the GitHub Advisory Database at 14 May 2022, 00:55 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.apache.ws.security:wss4jMaven<1.6.171.6.17
org.apache.wss4j:wss4j-ws-security-domMaven>=2.0.0, <2.0.22.0.2
Identifiers
GHSA-vjwc-5hfh-2vv5 · CVE-2015-0226
Weakness (CWE)
CWE-327
Published
14 May 2022
Updated
19 Feb 2025

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Apache WSS4J versions before 1.6.17 (org.apache.ws.security:wss4j) and 2.0.x before 2.0.2 (org.apache.wss4j:wss4j-ws-security-dom) leak information about decryption failures when decrypting encrypted keys or message data. A remote attacker who sends a series of crafted messages can use this to recover the plaintext of a symmetric key. Upgrade to wss4j 1.6.17 or wss4j-ws-security-dom 2.0.2.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.055, the 92nd percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:11 UTC First seen by agentprime
  2. 31 Oct 2026, 15:11 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.