Skip to main content

Threats Tagged 'cve-2026-71883'

View all threats tagged with 'cve-2026-71883'. Filter and sort to focus on specific types of threats.

Pro Console Lifetime

Stop chasing alerts. Route them.

Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.

Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)

View Plans & Pricing

API access activates after upgrading in Console -> Billing.

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now

Filter Threats

Narrow down the results by type, severity, or affected countries

Search threats by title, CVE ID, or description. Maximum 100 characters.
Active filters (1):Tag: cve-2026-71883

Threats Tagged 'cve-2026-71883'

Click on any threat for detailed analysis and mitigation recommendations

A vulnerability in Bouncy Castle for Java LTS before version 2.73.13 affects the one-shot native packet ciphers for AES modes including CBC, CCM, CFB, CTR, GCM, and GCM-SIV. The issue arises from improper handling of Java arrays in JNI calls, where input arrays are released in a way that copies key material back into the Java array, potentially overwriting ciphertext with the original key. This can cause applications encrypting in place over their key arrays to inadvertently expose raw AES keys instead of ciphertext. The pure-Java packet ciphers and streaming native modes are not affected. Bouncy Castle for Java (bcprov) is not affected as it does not include native implementations.

Join the discussion

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.

Join the discussion

Showing 1 to 2 of 2 results

Filters:Tag: cve-2026-71883
Page 1 of 1
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses