How severe is GHSA-p93r-85wp-75v3?

No CVSS score has been assigned to GHSA-p93r-85wp-75v3 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-p93r-85wp-75v3?

GHSA-p93r-85wp-75v3 affects the following packages: org.bouncycastle:bcprov-jdk15to18 (Maven), org.bouncycastle:bcprov-jdk14 (Maven), org.bouncycastle:bcprov-jdk18on (Maven). Ecosystems affected: Maven.

How do I fix GHSA-p93r-85wp-75v3?

Update org.bouncycastle:bcprov-jdk15to18 to 1.80.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p93r-85wp-75v3 is resolved across your whole dependency graph.

How do I detect GHSA-p93r-85wp-75v3 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.bouncycastle:bcprov-jdk15to18. 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.

How do I mitigate GHSA-p93r-85wp-75v3 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.

How does O3 Security protect against GHSA-p93r-85wp-75v3?

O3 pinpoints whether GHSA-p93r-85wp-75v3 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-p93r-85wp-75v3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-p93r-85wp-75v3 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 type of vulnerability is GHSA-p93r-85wp-75v3?

GHSA-p93r-85wp-75v3 is classified as CWE-385 (CWE-385). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-p93r-85wp-75v3 published, and has it been updated?

GHSA-p93r-85wp-75v3 was published on April 17, 2026 and was last updated on June 19, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-p93r-85wp-75v3

GHSA-p93r-85wp-75v3 is a CWE-385 vulnerability in org.bouncycastle:bcprov-jdk15to18. O3 Security confirms whether GHSA-p93r-85wp-75v3 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Bouncy Castle Has Covert Timing Channel Vulnerability

Also known asCVE-2026-5598

Published

Apr 17, 2026

Updated

Jun 19, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Blast Radius

3 pkgs affected

☕org.bouncycastle:bcprov-jdk15to18☕org.bouncycastle:bcprov-jdk14☕org.bouncycastle:bcprov-jdk18on

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

Covert timing channel vulnerability in Legion of the Bouncy Castle Inc. BC-JAVA core on all (core modules). This vulnerability is associated with program files FrodoEngine.Java.

This issue only affects users of the FrodoKEM algorithm involved in the decryption of encapsulations.

This issue affects BC-JAVA: from 1.71 to 1.80.1, 1.81, 1.82 to 1.83.

Fixed versions: 1.80.2, 1.81.1, 1.84

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.bouncycastle:bcprov-jdk15to18`	≥ 1.71&&< 1.80.2	1.80.2
☕Maven	`org.bouncycastle:bcprov-jdk14`	≥ 1.81&&< 1.81.1	1.81.1
☕Maven	`org.bouncycastle:bcprov-jdk18on`	≥ 1.82&&< 1.84	1.84

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.bouncycastle:bcprov-jdk15to18. 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.
Fix
Update org.bouncycastle:bcprov-jdk15to18 to 1.80.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p93r-85wp-75v3 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.
How O3 protects you
O3 pinpoints whether GHSA-p93r-85wp-75v3 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-p93r-85wp-75v3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Covert timing channel vulnerability in Legion of the Bouncy Castle Inc. BC-JAVA core on all (core modules). This vulnerability is associated with program files FrodoEngine.Java. This issue only affects users of the FrodoKEM algorithm involved in the decryption of encapsulations. This issue affects BC-JAVA: from 1.71 to 1.80.1, 1.81, 1.82 to 1.83. Fixed versions: 1.80.2, 1.81.1, 1.84

O3 Security · Impact-Aware SCA

Is GHSA-p93r-85wp-75v3 in your dependencies?

O3 detects GHSA-p93r-85wp-75v3 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works