Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

GHSA-72m5-fvvv-55m6

MEDIUM

GHSA-72m5-fvvv-55m6 is a medium-severity (CVSS 5.3) CWE-203 vulnerability in org.bouncycastle:bcprov-jdk14. O3 Security confirms whether GHSA-72m5-fvvv-55m6 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Observable Differences in Behavior to Error Inputs in Bouncy Castle

Also known asCVE-2020-26939
Published
Apr 22, 2021
Updated
Jul 17, 2025
Affected
8 pkgs
Patched
8 / 8
Exploits
None indexed

Blast Radius

8 pkgs affected
org.bouncycastle:bcprov-jdk14org.bouncycastle:bcprov-jdk15org.bouncycastle:bcprov-jdk16org.bouncycastle:bc-fipsorg.bouncycastle:bcprov-ext-jdk15onorg.bouncycastle:bcprov-ext-jdk16org.bouncycastle:bcprov-jdk15onorg.bouncycastle:bcprov-jdk15to18

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

In Legion of the Bouncy Castle BC before 1.55 and BC-FJA before 1.0.2, attackers can obtain sensitive information about a private exponent because of Observable Differences in Behavior to Error Inputs. This occurs in org.bouncycastle.crypto.encodings.OAEPEncoding. Sending invalid ciphertext that decrypts to a short payload in the OAEP Decoder could result in the throwing of an early exception, potentially leaking some information about the private exponent of the RSA private key performing the encryption.

Affected Packages

8 total 8 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.bouncycastle:bcprov-jdk14all versions1.61
Mavenorg.bouncycastle:bcprov-jdk15all versions1.61
Mavenorg.bouncycastle:bcprov-jdk16all versions1.61
Mavenorg.bouncycastle:bc-fipsall versions1.0.2
Mavenorg.bouncycastle:bcprov-ext-jdk15onall versions1.61
Mavenorg.bouncycastle:bcprov-ext-jdk16all versions1.61

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.bouncycastle:bcprov-jdk14. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update org.bouncycastle:bcprov-jdk14 to 1.61 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-72m5-fvvv-55m6 is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-72m5-fvvv-55m6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-72m5-fvvv-55m6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In Legion of the Bouncy Castle BC before 1.55 and BC-FJA before 1.0.2, attackers can obtain sensitive information about a private exponent because of Observable Differences in Behavior to Error Inputs. This occurs in org.bouncycastle.crypto.encodings.OAEPEncoding. Sending invalid ciphertext that decrypts to a short payload in the OAEP Decoder could result in the throwing of an early exception, potentially leaking some information about the private exponent of the RSA private key performing the encryption.
O3 Security · Impact-Aware SCA

Is GHSA-72m5-fvvv-55m6 in your dependencies?

O3 detects GHSA-72m5-fvvv-55m6 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.