Answer in brief
CVE-2026-8149 records a Medium severity vulnerability in Bouncy Castle LTS native GCM chunking can cause bad-tag exception on decryption. The current sources do not mark it as known exploited. The current feed maps org.bouncycastle:bcprov-lts8on (maven), org.bouncycastle:bcprov-lts8on (maven). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps org.bouncycastle:bcprov-lts8on (maven), org.bouncycastle:bcprov-lts8on (maven). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| org.bouncycastle:bcprov-lts8onmaven | >=2.73.0,<=2.73.10 | 2.73.11 |
| org.bouncycastle:bcprov-lts8onmaven | >=2.73.0 <2.73.11 | 2.73.11 |
Published upstream
May 8, 2026
Evidence: source:osv:source_dates:source-dates:recordSource modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:recordFirst seen by HOL
Jul 7, 2026
In Bouncy Castle LTS for Java, the AES/GCM native implementation used on Intel CPUs with AES PAA instruction sets (AVX / VAES / VAESF variants) can intermittently produce an incorrect authentication tag verification result during decryption when the ciphertext is fed in via a mix of `update()` calls followed by `doFinal()`. It is possible to work around it by either using `doFinal()` only (as the BCJSSE does) or by configuring the module to run in pure Java mode, by setting the system property "org.bouncycastle.native.cpu_variant" to java.
Quoted source text, attributed separately from HOL analysis.