How severe is GHSA-m26p-m559-g5j5?

No CVSS score has been assigned to GHSA-m26p-m559-g5j5 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-m26p-m559-g5j5?

GHSA-m26p-m559-g5j5 affects the following packages: bouncycastle:bcprov-jdk14 (Maven), bouncycastle:bcprov-jdk15 (Maven), bouncycastle:bcprov-jdk16 (Maven). Ecosystems affected: Maven.

How do I fix GHSA-m26p-m559-g5j5?

Update bouncycastle:bcprov-jdk14 to 1.38 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m26p-m559-g5j5 is resolved across your whole dependency graph.

How do I detect GHSA-m26p-m559-g5j5 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for bouncycastle:bcprov-jdk14, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-m26p-m559-g5j5 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-m26p-m559-g5j5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-m26p-m559-g5j5 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-m26p-m559-g5j5?

GHSA-m26p-m559-g5j5 has an EPSS (Exploit Prediction Scoring System) score of 2.4%, placing it in the 84th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-m26p-m559-g5j5 published, and has it been updated?

GHSA-m26p-m559-g5j5 was published on May 1, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

Legion of the Bouncy Castle Java Cryptography API Bleichenbacher Oracle VulnerabilityGHSA-m26p-m559-g5j5

GHSA-m26p-m559-g5j5 is a security vulnerability in bouncycastle:bcprov-jdk14. A fix is available for bouncycastle:bcprov-jdk14 — see the affected versions and patch details below.

Also known asCVE-2007-6721

Published

May 1, 2022

Updated

Nov 8, 2023

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs84th percentile — riskier than 84% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected

☕bouncycastle:bcprov-jdk14☕bouncycastle:bcprov-jdk15☕bouncycastle:bcprov-jdk16

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

The Legion of the Bouncy Castle Java Cryptography API before release 1.38, as used in Crypto Provider Package before 1.36, has unknown impact and remote attack vectors related to "a Bleichenbacher vulnerability in simple RSA CMS signatures without signed attributes."

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`bouncycastle:bcprov-jdk14`	all versions	1.38`bouncycastle:bcprov-jdk14:1.38`
☕Maven	`bouncycastle:bcprov-jdk15`	all versions	1.38`bouncycastle:bcprov-jdk15:1.38`
☕Maven	`bouncycastle:bcprov-jdk16`	all versions	1.38`bouncycastle:bcprov-jdk16:1.38`

Affected Products

2 products · 72 configurations

Application

bc-javabouncycastle

≤ 1.37

36 versions

1.011.021.031.041.051.061.071.081.091.101.111.12

Application

bouncy-castle-crypto-packagebouncycastle

≤ 1.35

34 versions

1.01.011.021.031.3.11.041.051.061.071.081.091.11

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for bouncycastle:bcprov-jdk14, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update bouncycastle:bcprov-jdk14 to 1.38 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m26p-m559-g5j5 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-m26p-m559-g5j5 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works