Skip to main content
CVE-2026-71883VulnerabilityPublished

In Bouncy Castle for Java LTS before 2.73.13, the one-shot native packet ciphers for AES-CBC, CCM, CFB, CTR, GCM and GCM-SIV released the caller's key, IV and additional authenticated data arrays with JNI's ReleaseByteArrayElements in mode 0, which commits the native copy back into the Java array

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-71883· High 8.2

Not known to be exploited · CVSS 8.2 High : upgrade to 2.73.13 soon.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.73.13
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/U:Amber

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade BC-LTS-JAVA and Legion of the Bouncy Castle Inc./bcprov-lts8on to 2.73.13.

Affected software

ProductAffectedFixed in
Legion of the Bouncy Castle Inc.BC-LTS-JAVAAffected
  • >=2.73.4 <2.73.13
Fixed in
  • 2.73.13
MavenLegion of the Bouncy Castle Inc./bcprov-lts8onpkg:maven/Legion of the Bouncy Castle Inc./bcprov-lts8onOther threatsAffected
  • >=2.73.4 <2.73.13
Fixed in
  • 2.73.13

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to Bouncy Castle for Java LTS version 2.73.13 or later where the issue is fixed by changing the JNI release mode to JNI_ABORT for read-only input arrays, preventing key data from overwriting ciphertext. Applications should avoid encrypting in place over key arrays as a best practice. No other mitigations are specified. Patch status is not explicitly stated but the description confirms the fix in version 2.73.13.

Description

In Bouncy Castle for Java LTS before 2.73.13, the one-shot native packet ciphers for AES-CBC, CCM, CFB, CTR, GCM and GCM-SIV released the caller's key, IV and additional authenticated data arrays with JNI's ReleaseByteArrayElements in mode 0, which commits the native copy back into the Java array. Those arrays are read-only to the native code, and on a JVM that returns a copy rather than a pin the copy still holds the input bytes as they were read. The output buffer is taken through a separate critical region and committed first, so where an application passed the same Java array as both an input and the destination - encrypting in place over KeyParameter.getKey(), for example - the later mode-0 release of the key wrote the unchanged key bytes over the ciphertext that had just been produced. The call still returned the correct output length, so an application encrypting in place over its own key array was handed the raw AES key where it expected ciphertext, with nothing in the API to indicate it, and would transmit or store the key in place of the message. The read-only input arrays are now released with JNI_ABORT, freeing the native copy without copying it back, and mode 0 is reserved for arrays the native code wrote. The pure-Java packet ciphers and the streaming native modes are not affected. Bouncy Castle for Java (bcprov) is not affected, as it ships no native implementations.

References

Community reviews

Loading reviews…