Skip to content
VulniPulse
Medium5.9Red Hat Linux

CVE-2026-71884: Red Hat org.bouncycastle:bcprov-lts8on: bouncycastle: Information disclosure via keystream reuse in native CTR cipher

This Red Hat advisory covers CVE-2026-71884.

Open the Red Hat advisory

Key facts

Vendor rating
Medium, CVSS 5.9
CVSS vector
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 · base score 8.2, scored by bcorgAttack vector: network. Attack complexity: low. Attack requirements: present. Privileges required: none. User interaction: none. Confidentiality impact on the vulnerable system: high. Integrity impact on the vulnerable system: none. Availability impact on the vulnerable system: none. Confidentiality impact on subsequent systems: none. Integrity impact on subsequent systems: none. Availability impact on subsequent systems: none.
Weakness
  • CWE-323 Reusing a Nonce, Key Pair in Encryption
EPSS
0.25% chance of exploitation in the next 30 days (16th percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: yes. Technical impact: partial. CISA, .
CISA KEV
Not listed (catalogue checked )
Affected
< 2.73.13
Source published
Listed by VulniPulse
Record changed

Compiled by VulniPulse from the linked sources. How records are collected and checked.

Affected products & platforms

Red Hat LinuxUnclassified

Description

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.

Text from the source record.

Affected versions
  • < 2.73.13

Official advisory · high-confidence parse· fetched ·verify at source

How to fix CVE-2026-71884

Vendor guidance

  • 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.

CVE-2026-71884 in other vendors' advisories

  • Atlassian: CVE-2026-71884, high severity, fixed in Bitbucket Data Center and Server: 10.5.2 Data Center Only, Bitbucket Data Center and Server: 10.2.9 (LTS) recommended Data Center Only, Bitbucket Data Center and Server: 9.4.27 (LTS) Data Center Only and 8 more

Compare every advisory for CVE-2026-71884

All Red Hat Linux advisories

Get an email when Red Hat publishes the next one.

See Red Hat's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about Red Hat