Application hang via unbounded native entropy retries
Published Aug 8, 2026 · Updated Aug 8, 2026
Denial of service in Bouncy Castle FIPS Java API 2.1.0 through 2.1.2 allows attackers to hang applications through native entropy requests. In rand_jni.c, NativeEntropySource reissues failed RDSEED or RDRAND instructions without a retry bound while the carry flag remains clear. The hang requires x86 or x86-64 native support and persistent instruction failure, leaving the calling thread uninterruptible inside JNI.
Summary
What happened
Denial of service in Bouncy Castle FIPS Java API 2.1.0 through 2.1.2 allows attackers to hang applications through native entropy requests. In rand_jni.c, NativeEntropySource reissues failed RDSEED or RDRAND instructions without a retry bound while the carry flag remains clear. The hang requires x86 or x86-64 native support and persistent instruction failure, leaving the calling thread uninterruptible inside JNI.
The record
- CVE
- CVE-2026-8798
- Published
- Aug 8, 2026
- Updated
- Aug 8, 2026
- Vendor
- Legion of the Bouncy Castle Inc.
- Product
- Bouncy Castle FIPS Java API
- Classifications
- CWE-835, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 8, 2026CVE publishedPublication date reported by the CVE source.
- Aug 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.1.0 <2.1.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo