CVE-2026-8798 Affecting opensearch-3-performance-analyzer package, versions <3.6.0-r1

Note: Versions mentioned in the description apply only to the upstream opensearch-3-performance-analyzer package and not the opensearch-3-performance-analyzer package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

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.

• https://www.cve.org/CVERecord?id=CVE-2026-8798
• https://github.com/advisories/GHSA-v6w3-qrh8-qccc
• https://osv.dev/vulnerability/MINI-3h75-p36f-9grj
• https://osv.dev/vulnerability/CVE-2026-8798
• https://github.com/bcgit/bc-java/wiki/CVE%E2%80%902026%E2%80%908798