CVE-2026-17508

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).

• CWE-770

• https://github.com/bcgit/bc-java/commit/20ed9e203caec91d25cd386ceb6d364e9b068f67
• https://github.com/bcgit/bc-java/commit/442393bf187c914b1e66fbed4fab532a1fe06c6a
• https://github.com/bcgit/bc-java/commit/480d878aa6f7dc8b20403064f304bbe0decbbb1a
• https://github.com/bcgit/bc-java/commit/766a31026ac24ed3c6cad8662058ba450c338da1
• https://github.com/bcgit/bc-java/commit/882fdab53f6c4c150a5d6a4e6ef1fc05d382385a
• https://github.com/bcgit/bc-java/commit/e72bc0681ff4227fced912ef7394daf7b7d57bb3
• https://github.com/bcgit/bc-java/wiki/CVE%E2%80%902026%E2%80%9017508

Published

Oct 2, 2026

Last Modified

Oct 2, 2026

Status

Awaiting Analysis

• 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.

• CVE-2026-17502IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote attacker t…7.5
• CVE-2026-17503IBM PowerVM Hypervisor FW1120.00 through FW1120.01, FW1110.0…5.1
• CVE-2026-17504IBM PowerVM Hypervisor FW1120.00 through FW1120.01, FW1110.0…4.4
• CVE-2026-17505The Translate Multilingual sites – TranslatePress plugin for…6.1
• CVE-2026-17506The Independent Analytics plugin for WordPress is vulnerable…7.2
• CVE-2026-17507In Bouncy Castle for Java before 1.86, the MLS implementatio…7.5
• CVE-2026-17509The WPML Multilingual CMS plugin for WordPress is vulnerable…6.5
• CVE-2026-1751A vulnerability has been discovered in GitLab CE/EE affectin…3.1
• CVE-2026-17510Crypt::OpenSSL::PKCS12 versions before 1.98 for Perl allow a…7.5
• CVE-2026-17511IBM PowerVM Hypervisor FW1120.00 through FW1120.01, FW1110.0…3.4
• CVE-2026-17512A vulnerability has been found in ggml-org whisper.cpp 1.8.4…3.3
• CVE-2026-17513A vulnerability was found in ggml-org whisper.cpp 95ea8f9b. …3.3