How severe is CVE-2015-0226?

CVE-2015-0226 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2015-0226 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 6% (93rd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2015-0226?

CVE-2015-0226 primarily affects Apache Wss4j. In total, 5 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2015-0226?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2015-0226 published?

CVE-2015-0226 was published on 2017-10-30 and last updated on 2026-06-17.

CVE-2015-0226

CVE-2015-0226 is a high-severity vulnerability in Apache Wss4j with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-327.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v2: 5.0
EPSS exploit prediction: 6% (93rd percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-327
Affected product: Apache Wss4j
Published: 2017-10-30
Last modified: 2026-06-17

Description

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 plaintext form of a symmetric key via a series of crafted messages. NOTE: this vulnerability exists because of an incomplete fix for CVE-2011-2487.

Frequently asked questions

What is CVE-2015-0226?: 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 plaintext form of a symmetric key via a series of crafted messages. NOTE: this vulnerability exists because of an incomplete fix for CVE-2011-2487.
How severe is CVE-2015-0226?: CVE-2015-0226 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2015-0226 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 6% (93rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2015-0226?: CVE-2015-0226 primarily affects Apache Wss4j. In total, 5 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2015-0226?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2015-0226 published?: CVE-2015-0226 was published on 2017-10-30 and last updated on 2026-06-17.

References

Affected products (5)

cpe:2.3:a:apache:wss4j:*:*:*:*:*:*:*:*
cpe:2.3:a:apache:wss4j:2.0:beta:*:*:*:*:*:*
cpe:2.3:a:apache:wss4j:2.0.0:*:*:*:*:*:*:*
cpe:2.3:a:apache:wss4j:2.0.0:rc1:*:*:*:*:*:*
cpe:2.3:a:apache:wss4j:2.0.1:*:*:*:*:*:*:*

More vulnerabilities in Apache Wss4j

CVE-2026-88920 — Critical (CVSS 9.8): An authentication bypass in the DOM security processor in Apache WSS4J allows unauthenticated remote attackers to forge…
CVE-2026-89238 — Critical (CVSS 9.1): WSS4J EncryptedHeader child confusion could promote an attacker-controlled plaintext element as the decrypted header,…
CVE-2026-87830 — Critical (CVSS 9.1): In the StAX streaming WS-SecurityPolicy validator, certain relative or unsupported XPath expressions can be converted…
CVE-2020-13936 — High (CVSS 8.8): An attacker that is able to modify Velocity templates may execute arbitrary Java code or run arbitrary system commands…
CVE-2026-95616 — High (CVSS 7.5): An integer overflow in WSS4J's DER bounds check lets an oversized allocation pass validation. An unauthenticated…
CVE-2026-92121 — High (CVSS 7.5): In the WSS4J streaming (StAX) code, a signature reference using the WS-Security STR-Transform leaves an internal…

All CVEs affecting Apache Wss4j →

Other CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) vulnerabilities

CVE-2026-50086 — Critical (CVSS 10.0): The Aqara IAM/SSO gateway (gw-builder.aqara.com) exposes bidirectional AES round-trups against the platform's signing…
CVE-2026-21718 — Critical (CVSS 10.0): An authentication bypass vulnerability exists in Copeland XWEB Pro version 1.12.1 and prior, enabling any attackers to…
CVE-2025-54426 — Critical (CVSS 9.9): Polkadot Frontier is an Ethereum and EVM compatibility layer for Polkadot and Substrate. In versions prior to commit…
CVE-2024-51478 — Critical (CVSS 9.9): YesWiki is a wiki system written in PHP. Prior to 4.4.5, the use of a weak cryptographic algorithm and a hard-coded…
CVE-2026-76133 — Critical (CVSS 9.8): The affected Ebyte product uses a deprecated hashing algorithm in an authentication-related operation. Under…
CVE-2026-28252 — Critical (CVSS 9.8): A Use of a Broken or Risky Cryptographic Algorithm vulnerability in Trane Tracer SC, Tracer SC+, and Tracer Concierge…

Browse all CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) vulnerabilities →