CVE-2026-63573
Last modified
CVE-2026-63573 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. Observable discrepancy in the CMS RSA PKCS#1 v1.5 key-transport unwrap (KeyTransRecipientInformation.UnwrapKey) in Legion of the Bouncy Castle Inc. bc-csharp before 2.7.0 allows a remote attacker who holds a captured CMS EnvelopedData message, and who can submit many modified messages to an application that decrypts them with the recipient's RSA private key and reveals how decryption failed, to recover the captured message's content-encryption key and so its content, via a Bleichenbacher-style adaptive chosen-ciphertext attack, because a key-transport ciphertext with invalid PKCS#1 v1.5 padding is rejected during unwrap with a distinct "bad padding in message." CmsException instead of being replaced by a random key, so it can be told apart from a correctly padded ciphertext, which fails only later at content decryption.. EPSS estimates a 0.31% chance of exploitation in the next 30 days.
Description
Observable discrepancy in the CMS RSA PKCS#1 v1.5 key-transport unwrap (KeyTransRecipientInformation.UnwrapKey) in Legion of the Bouncy Castle Inc. bc-csharp before 2.7.0 allows a remote attacker who holds a captured CMS EnvelopedData message, and who can submit many modified messages to an application that decrypts them with the recipient's RSA private key and reveals how decryption failed, to recover the captured message's content-encryption key and so its content, via a Bleichenbacher-style adaptive chosen-ciphertext attack, because a key-transport ciphertext with invalid PKCS#1 v1.5 padding is rejected during unwrap with a distinct "bad padding in message." CmsException instead of being replaced by a random key, so it can be told apart from a correctly padded ciphertext, which fails only later at content decryption.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Bouncycastle | Bc-Csharp | < 2.7.0 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-63573?
How severe is CVE-2026-63573?
How do I fix CVE-2026-63573?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-63568Allocation of resources without limits or throttling in the …7.5
- CVE-2026-63569Improper input validation in DHAgreement.CalculateAgreement …6.5
- CVE-2026-6357pip prior to version 26.1 would run self-update check functi…5.3
- CVE-2026-63570Loop with unreachable exit condition in Pkcs12Store.GetCerti…7.5
- CVE-2026-63571Improper verification of cryptographic signature in the attr…7.5
- CVE-2026-63572Allocation of resources without limits in PKCS#12 keystore l…7.5
- CVE-2026-63574Memory allocation with excessive size value in the OpenPGP s…7.5
- CVE-2026-63575Loop with unreachable exit condition in the PKCS#12 key deri…7.5
- CVE-2026-63576Improper certificate validation in PkixNameConstraintValidat…7.5
- CVE-2026-63577Improper certificate validation in the directoryName name-co…7.5
- CVE-2026-63578Allocation of resources without limits in password-based pri…7.5
- CVE-2026-6358Use after free in XR in Google Chrome on Android prior to 14…8.8
Are you affected by CVE-2026-63573?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
