VYPR
Vypr IntelligenceAI-generatedOct 2, 2026· 21 CVEs

Bouncy Castle bc-csharp: 21 Crypto Flaws Disclosed Together, Affecting Key Security Functions

Legion of the Bouncy Castle Inc.'s bc-csharp library patched 21 high/critical vulnerabilities disclosed together on Oct 2, 2026, impacting crypto operations.

Key findings

  • 21 vulnerabilities disclosed in Legion of the Bouncy Castle Inc.'s bc-csharp library, all fixed in version 2.7.0.
  • Flaws include improper certificate validation, allowing forged certificates and bypass of name constraints.
  • Multiple vulnerabilities lead to denial of service via CPU exhaustion or memory allocation issues.
  • Critical flaw CVE-2026-63569 allows an on-path attacker to defeat key authentication in Diffie-Hellman.
  • Issues affect various cryptographic functions including PKI, OpenPGP, DTLS, and AES-CCM modes.

On October 2, 2026, a batch of 21 high and critical severity vulnerabilities was disclosed in Legion of the Bouncy Castle Inc.'s bc-csharp library, affecting all versions prior to 2.7.0. These vulnerabilities, disclosed within a one-hour window, span a range of cryptographic weaknesses including improper certificate validation, resource allocation issues leading to denial of service, and flaws in cryptographic signature verification. The timely disclosure of this batch highlights potential risks for applications relying on bc-csharp for secure cryptographic operations.

Several vulnerabilities stem from improper certificate validation. CVE-2026-63577 and CVE-2026-103602 detail how improper validation in PkixNameConstraintValidator can allow attackers controlling or obtaining certificates from a name-constrained intermediate CA to bypass name constraints and have forged certificates accepted by PKIX. Similarly, CVE-2026-63576 points to a bypass of permitted or excluded uniformResourceIdentifiers through name-constrained subordinate CAs. CVE-2026-63571 describes an improper verification of cryptographic signatures in the attribute certificate path validator, potentially allowing forged X.509 attribute certificates to be accepted as valid.

A significant number of vulnerabilities relate to resource allocation issues and inefficient algorithms, leading to denial of service (DoS) conditions. CVE-2026-63578, CVE-2026-63572, and CVE-2026-63568 describe resource allocation without limits or throttling in password-based private-key decryption, PKCS#12 keystore loading, and CMP/CRMF MAC verification, respectively. These can lead to CPU exhaustion. CVE-2026-63574 and CVE-2026-103600 involve memory allocation with excessive size values in OpenPGP signature and user attribute subpacket parsers, and uncontrolled recursion in the ASN.1 parser, respectively, both leading to memory exhaustion. CVE-2026-103604 details inefficient algorithmic complexity in X.509 distinguished name string conversion, also resulting in DoS through CPU exhaustion. CVE-2026-63570 describes a loop with an unreachable exit condition in PKCS#12 keystore loading, causing DoS. CVE-2026-103603 points to excessive memory allocation in HSS/LMS signature code, leading to denial of service. CVE-2026-63566 involves memory allocation with excessive size in DTLS handshake reassembly, causing DoS.

Other critical flaws include CVE-2026-63567, a CBC padding-oracle attack in IesEngine.DecryptBlock that could recover plaintext, and CVE-2026-16001, an exposure of the message authentication key through the encryption keystream in IesEngine's stream mode, allowing for forgery of shorter messages. CVE-2026-16000 and CVE-2026-15999 detail issues in AES-CCM mode implementations, specifically a missing cryptographic step and improper validation of integrity check values, respectively, which could allow for forged ciphertexts. CVE-2026-63573 describes an observable discrepancy in CMS RSA PKCS#1 v1.5 key-transport unwrap, potentially allowing for decryption of captured CMS EnvelopedData messages.

The most severe vulnerability, CVE-2026-63569, is a critical improper input validation in DHAgreement.CalculateAgreement (MTI/A0 two-pass Diffie-Hellman). This allows an on-path attacker to force the local party to compute an agreed value the attacker already knows, defeating the key authentication provided by MTI/A0.

All 21 vulnerabilities were fixed in version 2.7.0 of the bc-csharp library. Users are strongly advised to update to this version to mitigate these risks. The comprehensive nature of this batch underscores the importance of regular security audits and prompt patching for cryptographic libraries.

The batch includes the following CVE IDs: CVE-2026-63578, CVE-2026-63577, CVE-2026-63576, CVE-2026-63575, CVE-2026-63574, CVE-2026-63573, CVE-2026-63572, CVE-2026-63571, CVE-2026-63570, CVE-2026-103604, CVE-2026-103603, CVE-2026-103602, CVE-2026-103601, CVE-2026-103600, CVE-2026-63569, CVE-2026-63568, CVE-2026-63567, CVE-2026-63566, CVE-2026-16001, CVE-2026-16000, CVE-2026-15999.

AI-written article. Grounded in 21 CVE records listed below.