CVE-2026-85515 Legion of the Bouncy Castle Inc. CVE debrief

Who should care

Defenders and developers using Bouncy Castle for Java before 1.86 should assess exposure and implement integrity checks for OpenPGP encrypted messages. This includes reviewing system deployments, checking for affected versions, and ensuring that integrity checks are in place to prevent potential truncation attacks. Additionally, security teams and vulnerability management teams should be aware of the potential risks and take necessary actions to mitigate

Why it matters

The vulnerability in Bouncy Castle for Java before 1.86 allows for truncated OpenPGP encrypted messages to be accepted without error, potentially leading to integrity issues. Defenders and developers should assess exposure and implement integrity checks for OpenPGP encrypted messages.

• Potential integrity issues with OpenPGP encrypted messages
• Possible truncation attacks on encrypted messages
• Need for integrity checks on encrypted messages
• Verification of Bouncy Castle for Java version

Technical summary

The vulnerability in Bouncy Castle for Java before 1.86 allows for truncated OpenPGP encrypted messages to be accepted without error. This affects the SEIPD version 1 path with no integrity check performed. The issue also affects Bouncy Castle for Java LTS before 2.73.13 and Bouncy Castle for Java FIPS before specific versions. The fix involves changes to the AEAD decryption streams and the OpenPGPMessageInputStream.

Defensive priority

High

Recommended defensive actions

• Review and update Bouncy Castle for Java to version 1.86 or later
• Implement integrity checks for OpenPGP encrypted messages
• Monitor for potential truncation attacks
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review compensating controls for exposed systems while remediation is scheduled and verified

Evidence notes

The vulnerability was detected in Bouncy Castle for Java before 1.86. The issue affects the SEIPD version 1 path and the AEAD path. The low-level API is unaffected. The fix involves changes to the AEAD decryption streams and the OpenPGPMessageInputStream.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.