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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-p93r-85wp-75v3 can be triaged on real exposure rather than presence alone.

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 is the EPSS score for GHSA-p93r-85wp-75v3?

GHSA-p93r-85wp-75v3 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 58th 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.

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 September 10, 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

Not in CISA KEV

GHSA-p93r-85wp-75v3 — bcprov-jdk15to18

Fix: bcgit/bc-java@8692e6b

GHSA-p93r-85wp-75v3 is a CWE-385 vulnerability in org.bouncycastle:bcprov-jdk15to18. A fix is available for org.bouncycastle:bcprov-jdk15to18 — see the affected versions and patch details below.

Bouncy Castle Has Covert Timing Channel Vulnerability

Also known asCVE-2026-5598

Published

Apr 17, 2026

Updated

Sep 10, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-p93r-85wp-75v3.

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs58th percentile — riskier than 58% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

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`org.bouncycastle:bcprov-jdk15to18:1.80.2`
☕Maven	`org.bouncycastle:bcprov-jdk14`	≥ 1.81&&< 1.81.1	1.81.1`org.bouncycastle:bcprov-jdk14:1.81.1`
☕Maven	`org.bouncycastle:bcprov-jdk18on`	≥ 1.82&&< 1.84	1.84`org.bouncycastle:bcprov-jdk18on: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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-p93r-85wp-75v3 can be triaged on real exposure rather than presence alone.

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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

To exploit this issue, an unauthenticated attacker needs to send highly specific, malformed ciphertexts to the target server. These payloads are used to interact with the private key of the server in a way that the vulnerable, non-constant time code paths are triggered during the verification step. An attack typically…

Product	Fixed in	Advisory
Red Hat JBoss Enterprise Application Platform 7	see advisory	RHSA-2026:12269
Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 7	`eap7-bouncycastle-0:1.84.0-1.redhat_00001.1.el7eap`	RHSA-2026:12267
Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 7	`eap7-activemq-artemis-0:2.16.0-22.redhat_00057.1.el7eap`	RHSA-2026:53644
Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 8	`eap7-activemq-artemis-0:2.16.0-22.redhat_00057.1.el8eap`	RHSA-2026:53645
Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 9	`eap7-activemq-artemis-0:2.16.0-22.redhat_00057.1.el9eap`	RHSA-2026:53646
Red Hat JBoss Enterprise Application Platform 8.1.7.GA	`org.bouncycastle/bcprov-jdk18on:1.84.0.redhat-00001`	RHSA-2026:18059
Red Hat JBoss Enterprise Application Platform 8.1 for RHEL 8	`eap8-bouncycastle-0:1.84.0-1.redhat_00001.1.el8eap`	RHSA-2026:18054
Red Hat JBoss Enterprise Application Platform 8.1 for RHEL 9	`eap8-bouncycastle-0:1.84.0-1.redhat_00001.1.el9eap`	RHSA-2026:18055

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 Security finds GHSA-p93r-85wp-75v3 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works