Staging Environment: Content and features may be unstable or change without notice.

Advisory Weakness Curation

CVE-2026-8149

Progress 0 / 0

Advisory Summaries

github_osv/GHSA-mx76-r943-rf8g

Bouncy Castle LTS native GCM chunking can cause bad-tag exception on decryption 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.

gitlab/maven/org.bouncycastle/bc-fips/CVE-2026-8149

Bouncy Castle has a vulnerability in program files gcm128w, gcm512w A vulnerability in Legion of the Bouncy Castle Inc. BC-FJA BC-FIPS on Linux, X86_64, AVX, AVX-512f. This vulnerability is associated with program files gcm128w, gcm512w. This issue affects BC-FJA: from 2.1.0 through 2.1.2.

gitlab/maven/org.bouncycastle/bcprov-lts8on/CVE-2026-8149

Bouncy Castle LTS native GCM chunking can cause bad-tag exception on decryption 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.