All reports
Medium

Bouncy Castle LTS native GCM chunking can cause bad-tag exception on decryption

Affected versions

Affected versions
>= 2.73.0, <= 2.73.10
Fixed version
2.73.11

Exploitation

CVE-2026-8149

Probability of exploitation in the next 30 days: 0.16%

FIRST EPSS · 2026-11-19

Description

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.

Links

Credits

  • discerningdev