Threats affecting pkg:github/bcpkix

In Bouncy Castle for Java before 1.86, several password-based key derivation entry points ran the KDF with cost parameters taken from the untrusted input being processed, without bounding them, so a small input could dictate an arbitrary amount of work before any password or integrity check could reject it. The affected paths are the RFC 9579 PBMAC1 MAC calculator builders, which took the PBKDF2 iteration count and derived-key length straight out of PBMAC1Params (JcePBMac1CalculatorBuilder, and PKCS12PBEUtils.createPBMac1Calculator reached from PKCS12PfxPdu.isMacValid); the scrypt parallelization parameter p in the PKCS#8 and PKCS#12 cost guards, which bounded only the cost parameter N and the block size r even though the scratch buffer scales with r times p, so the configured memory ceiling could be evaded entirely; the raw JCA PBKDF2 provider (org.bouncycastle.jcajce.provider.symmetric.PBEPBKDF2); and the bcrypt round count read from an encrypted OpenSSH v1 private key's own kdfoptions. Each now bounds the parameter before deriving, in line with the caps already applied elsewhere in the tree, with the OpenSSH round count configurable through the new org.bouncycastle.openssh.max_rounds property. This completes the bounding begun in 1.85 for the PKCS#8 / PBES2 decryptors (CVE-2026-15055). This issue also affects Bouncy Castle for Java LTS before 2.73.13, and Bouncy Castle for Java FIPS (BC-FJA) before bcpkix-fips 1.0.13 (1.0.X series), 2.0.13 (2.0.X series) and 2.1.13 (2.1.X series).

CVE-2026-12802 is a high-severity vulnerability in Legion of the Bouncy Castle Inc.'s BC-JAVA library. It involves improper validation of the integrity check value in the CMS AuthEnvelopedData decryption process, specifically failing to enforce tag-length. This affects versions of Bouncy Castle for Java before 1.85 and certain LTS and FIPS versions prior to specified patch releases.

CVE-2026-59639 is a high severity vulnerability in Legion of the Bouncy Castle Inc.'s BC-JAVA library. The issue occurs in versions before 1.85 and certain 2.73.x versions, where the CMS verifySignatures method incorrectly returns true for SignedData objects that have zero signers. This improper verification of cryptographic signatures can undermine the trustworthiness of signature validation in affected versions.

CVE-2026-59642 is a high-severity vulnerability in Bouncy Castle for Java (BC-JAVA) affecting versions before 1.85 and certain LTS and FIPS versions prior to specified patch releases. The issue involves improper validation of the integrity check value in CMS AuthenticatedData when authenticated attributes are present, meaning the content is not properly bound to the MAC. This could undermine the integrity guarantees of the cryptographic message syntax implementation.

CVE-2026-59647 is a medium severity vulnerability in Bouncy Castle for Java where the CRMF/CMP password-MAC implementation honors an unbounded iteration count. This affects versions before 1.85, and versions from 2.73.0 up to but not including 2.73.12. The issue relates to allocation of resources without limits or throttling, potentially leading to resource exhaustion.

Use of a Broken or Risky Cryptographic Algorithm vulnerability in Legion of the Bouncy Castle Inc. BC-JAVA bcpkix on all (pkix modules), Legion of the Bouncy Castle Inc. BCPKIX-FIPS bcpkix on All (pkix modules), Legion of the Bouncy Castle Inc. BCPIX-LTS bcpkix on All (pkix modules). This vulnerability is associated with program files JcaContentVerifierProviderBuilder.Java, JcaContentVerfierProviderBuilder.Java. This issue affects BC-JAVA: from 1.67 before 1.80.2, from 1.81 before 1.81.1, from 1.82 before 1.84; BCPKIX-FIPS: from 2.0.6 before 2.0.11, from 2.1.7 before 2.1.11; BCPIX-LTS: from 2.73.7 before 2.73.11.