Observable discrepancy in the CMS RSA PKCS#1 v1.5 key-transport unwrap (KeyTransRecipientInformation.UnwrapKey) in Legion of the Bouncy Castle Inc. (CVE-2026-63573)
A vulnerability in Legion of the Bouncy Castle Inc. bc-csharp before version 2.7.0 allows a remote attacker to recover the content-encryption key of a captured CMS EnvelopedData message. This is due to an observable discrepancy in the RSA PKCS#1 v1.5 key-transport unwrap process, where invalid padding errors are distinguishable from other decryption failures. This enables a Bleichenbacher-style adaptive chosen-ciphertext attack.
AI Analysis
Technical Summary
The vulnerability exists in the CMS RSA PKCS#1 v1.5 key-transport unwrap function (KeyTransRecipientInformation.UnwrapKey) in Legion of the Bouncy Castle Inc. bc-csharp versions prior to 2.7.0. When decrypting a CMS EnvelopedData message, if the RSA private key unwrap operation encounters invalid PKCS#1 v1.5 padding, it throws a distinct "bad padding in message." CmsException instead of replacing the key with a random value. This difference in error messages allows a remote attacker, who can submit many modified ciphertexts to the decryption application and observe the failure mode, to perform a Bleichenbacher-style adaptive chosen-ciphertext attack to recover the content-encryption key and thus decrypt the message content.
Potential Impact
An attacker who has captured a CMS EnvelopedData message and can interact with the decryption service to submit multiple modified ciphertexts can exploit this vulnerability to recover the content-encryption key. This compromises the confidentiality of the encrypted message content. The vulnerability does not require privileges or user interaction but does require the ability to submit ciphertexts and observe distinct error responses.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, applications should avoid revealing distinct error messages that differentiate padding errors from other decryption failures during RSA PKCS#1 v1.5 unwrap operations. Implementing uniform error handling to prevent attackers from distinguishing error types can mitigate the risk of this adaptive chosen-ciphertext attack.
Observable discrepancy in the CMS RSA PKCS#1 v1.5 key-transport unwrap (KeyTransRecipientInformation.UnwrapKey) in Legion of the Bouncy Castle Inc. (CVE-2026-63573)
Description
A vulnerability in Legion of the Bouncy Castle Inc. bc-csharp before version 2.7.0 allows a remote attacker to recover the content-encryption key of a captured CMS EnvelopedData message. This is due to an observable discrepancy in the RSA PKCS#1 v1.5 key-transport unwrap process, where invalid padding errors are distinguishable from other decryption failures. This enables a Bleichenbacher-style adaptive chosen-ciphertext attack.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability exists in the CMS RSA PKCS#1 v1.5 key-transport unwrap function (KeyTransRecipientInformation.UnwrapKey) in Legion of the Bouncy Castle Inc. bc-csharp versions prior to 2.7.0. When decrypting a CMS EnvelopedData message, if the RSA private key unwrap operation encounters invalid PKCS#1 v1.5 padding, it throws a distinct "bad padding in message." CmsException instead of replacing the key with a random value. This difference in error messages allows a remote attacker, who can submit many modified ciphertexts to the decryption application and observe the failure mode, to perform a Bleichenbacher-style adaptive chosen-ciphertext attack to recover the content-encryption key and thus decrypt the message content.
Potential Impact
An attacker who has captured a CMS EnvelopedData message and can interact with the decryption service to submit multiple modified ciphertexts can exploit this vulnerability to recover the content-encryption key. This compromises the confidentiality of the encrypted message content. The vulnerability does not require privileges or user interaction but does require the ability to submit ciphertexts and observe distinct error responses.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, applications should avoid revealing distinct error messages that differentiate padding errors from other decryption failures during RSA PKCS#1 v1.5 unwrap operations. Implementing uniform error handling to prevent attackers from distinguishing error types can mitigate the risk of this adaptive chosen-ciphertext attack.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-xx4m-xv2j-xx6g
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-63573"]
- Database Specific Severity
- HIGH
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6abfeeb7a43b0b3b89e5609c
Added to database: 10/02/2026, 17:49:43 UTC
Last enriched: 10/02/2026, 18:20:45 UTC
Last updated: 10/02/2026, 19:45:56 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.