cve.bz

CVE-2026-71884 legion of the bouncy castle inc. bc-lts-java: Reusing a Nonce, Key Pair in Encryption

8.2 highEPSS 0.3%

High (8.2) in legion of the bouncy castle inc. bc-lts-java. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
In Bouncy Castle for Java LTS before 2.73.13, the native one-shot CTR packet cipher did not check that the requested input length fitted the counter space the IV left. In CTR mode the IV and the block counter share one 16-byte block, so an IV of 13 to 15 bytes leaves a counter of only 1 to 3 bytes, addressing 256, 65536 or 16777216 blocks respectively. Given a longer input the counter wrapped and the keystream repeated from the start of the same packet, and the call then returned the full input length as though every byte had been correctly transformed. Two segments of the message were therefore encrypted under the same keystream, so their plaintexts can be recovered from the ciphertext alone, without the key, while the caller saw neither an exception nor a short length to indicate it. The streaming implementation validates at init and again while processing, and the portable AESCTRPacketCipher rejects such a request with "Counter in CTR/SIC mode out of range.", but the native one-shot path has a single entry point and performed no counter-range validation there. It now preflights the IV-derived counter range and rejects an over-long request before any output is written, so the operation is failure-atomic and never reports success for bytes it did not correctly transform. A counter of four bytes or more cannot be exhausted by a Java int length and is unaffected, as is a full 16-byte IV, where the counter range is the caller's responsibility. Bouncy Castle for Java (bcprov) is not affected, as it ships no native implementations.

Severity

CVSS 4.0

8.2 high
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
EPSS
0.3% (unchanged from 0.3% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 17th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-10-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-323 Reusing a Nonce, Key Pair in Encryption
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-71884 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-71884?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-71884?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-71884 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • legion of the bouncy castle inc.:bc-lts-java

Versions

From the CNA's record in the CVE List.

ProductAffected
Legion of the Bouncy Castle Inc. BC-LTS-JAVAfrom 2.73.4 before 2.73.13

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A flaw was found in Bouncy Castle's native one-shot Counter (CTR) mode cipher implementation. When processing a message with a short counter space (initialization vector of 13 to 15 bytes), the native path fails to validate if the input length exceeds the available counter range. Processing an overly long input causes the block counter to wrap, leading to keystream repetition within the same packet. A remote unauthenticated attacker can exploit this keystream reuse to recover sensitive plaintext directly from the ciphertext without knowing the encryption key.

Red Hat's mitigation

Configure applications using Bouncy Castle to use Java-based streaming CTR mode ciphers or ensure Initialization Vectors (IVs) are restricted to 12 bytes or fewer to prevent counter exhaustion. Alternatively, enforce application-level input payload limits that do not exceed the counter space.

ProductPackageStateAdvisory
Red Hat build of Apicurio Registry 3bcprov-lts8onAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-71884.

References

Check your stackJSON