8.7

CVE-2026-8798: legion of the bouncy castle inc. bc-fja Infinite Loop

CVSS: 8.7v4.0HighAwaiting analysis
AliasesUBUNTU-CVE-2026-8798CGA-prjf-5cfx-wwh5CGA-wmwh-qvx6-mffm
Published 08-08-2026Last modified 10-08-2026

Vulnerability summary

CVE-2026-8798 is a high (CVSS 8.7) Infinite Loop vulnerability in legion of the bouncy castle inc. bc-fja. EPSS estimates a 0.43% chance of exploitation in the next 30 days, higher than 35.9% of scored vulnerabilities.

Overall risk
35/100
0100
Medium · default modelHow is this calculated?
CVSS score
8.7/10
010
High · v4.0 (CVE.org)
EPSS score
0.43%
0%100%
Low · +0.10 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 0 · Related 1

Timeline

  1. 08-08-2026
    PublishedVulnerability first disclosed.
  2. 10-08-2026
    Last modifiedVulnerability information updated.

Description

In Bouncy Castle for Java FIPS (BC-FJA) before bc-fips 2.1.3, the native entropy source used on Intel platforms retried the CPU entropy instructions without any bound. RDSEED and RDRAND report failure through their carry flag, and the JNI seeding routine spun re-issuing the instruction for as long as that flag stayed clear, so a persistent failure of the on-chip entropy source - whether from a hardware fault, from the underlying DRBG being exhausted by contention across many cores, or from a hypervisor that does not provide the instruction - left the calling thread looping indefinitely inside the JNI call, where it could be neither interrupted nor timed out. Any operation drawing from the native entropy source could therefore hang, denying service to the application. The retry loops are now bounded (200 attempts for RDSEED and 20 for RDRAND, twice the baselines given in Intel's Digital Random Number Generator software implementation guide), pausing between attempts and, on exhaustion, clearing any partially written buffer and throwing rather than continuing to spin. The clear is performed by an un-elidable memzero, which uses a volatile pointer and an assembly memory barrier so that a compiler cannot optimise the erase away as a dead store. Bouncy Castle for Java (bcprov) is not affected, as it has no native entropy source; the 1.0.X and 2.0.X FIPS series are not affected.

CVSS metrics

6 scores · 6 sources · 1 version

EPSS trend

Probability

0.43%

Chance of exploitation in the next 30 days

Percentile

36%

Versus all other CVEs

30-day change

+0.10 pp

From 0.33% on 21-09-2026

21-09-202621-10-2026
EPSS score
0.43%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Chainguard10 products
  • bouncycastle-fips< 2.1.3-r0
  • guacamole-client-extensions< 1.6.0-r16
  • keycloak-fips-26.6< 26.6.7-r1
  • keycloak-fips-26.6-iamguarded-fips< 26.6.7-r1
  • keycloak-fips-26.7< 26.7.4-r1
Legion of the bouncy castle inc.1 product
Org.bouncycastle1 product
  • bc-fips≥ 2.1.0, < 2.1.3
Ubuntu1 product
  • bouncycastleAll versions (No fix recorded)
Wolfi1 product
  • opensearch-2< 2.19.6-r11

5 vendors · 14 products

References

5 links