# Bouncy Castle: the native entropy source used on Intel platforms retried the CPU entropy instructions without any bound

Advisory record · `GHSA-v6w3-qrh8-qccc`

- **Identifiers:** `GHSA-v6w3-qrh8-qccc` · `CVE-2026-8798`
- **State:** Confirmed
- **Severity:** CVSS 8.7 High
- **Critical:** No
- **Weakness (CWE):** [CWE-835](https://cwe.mitre.org/data/definitions/835.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Published:** 8 Aug 2026
- **Updated:** 18 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 8 Aug 2026, 03:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.bouncycastle:bc-fips` (Maven): affected `>=2.1.0, <2.1.3`; fixed in `2.1.3`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Bouncy Castle for Java FIPS (bc-fips) versions 2.1.0 before 2.1.3 are vulnerable. A failure of the Intel CPU entropy instructions could leave a thread looping indefinitely inside a native call, and any operation drawing from that entropy source could hang, causing denial of service. The source does not describe the attacker's access requirements. Upgrade to bc-fips 2.1.3 or later.

Written 2 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.7 High, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/U:Amber`, from CNA (bcorg)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0043, the 37th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:16 UTC: First seen by agentprime
- 31 Oct 2026, 14:16 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-v6w3-qrh8-qccc)

## Sources

- [GitHub Advisory Database: GHSA-v6w3-qrh8-qccc](https://github.com/advisories/GHSA-v6w3-qrh8-qccc)
- [OSV: GHSA-v6w3-qrh8-qccc](https://osv.dev/vulnerability/GHSA-v6w3-qrh8-qccc)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-8798>
- <https://github.com/bcgit/bc-java>
- <https://github.com/bcgit/bc-java/wiki/CVE%E2%80%902026%E2%80%908798>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-v6w3-qrh8-qccc>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-v6w3-qrh8-qccc/>. Everything for agents: <https://agentprime.io/llms.txt>.