[From nobody Mon Sep 28 09:19:14 2026 Received: (at submit) by bugs.debian.org; 3 Aug 2026 19:11:44 +0000 X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02 (2024-03-25) on buxtehude.debian.org X-Spam-Level: X-Spam-Status: No, score=-9.9 required=4.0 tests=BAYES_00, FOURLA, FROMDEVELOPER, NO_RELAYS,XMAILER_REPORTBUG autolearn=ham autolearn_force=no version=4.0.1-bugs.debian.org_2005_01_02 X-Spam-Bayes: score:0.0000 Tokens: new, 243; hammy, 150; neutral, 245; spammy, 0. spammytokens: hammytokens:0.000-+--XDebbugsCc, 0.000-+--X-Debbugs-Cc, 0.000-+--H*F:U*carnil, 0.000-+--H*Ad:N*Bug, 0.000-+--HTo:N*Debian Return-path: <carnil@debian.org> Received: via submission by buxtehude.debian.org with esmtp (Exim 4.96) (envelope-from <carnil@debian.org>) id 1wqy4d-00CGcT-1r for submit@bugs.debian.org; Mon, 03 Aug 2026 19:11:43 +0000 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Salvatore Bonaccorso <carnil@debian.org> To: Debian Bug Tracking System <submit@bugs.debian.org> Subject: bouncycastle: CVE-2026-12185 CVE-2026-12802 CVE-2026-12803 CVE-2026-12816 CVE-2026-12817 CVE-2026-12852 CVE-2026-12860 CVE-2026-13506 CVE-2026-13586 CVE-2026-14682 CVE-2026-15055 CVE-2026-58059 CVE-2026-58060 CVE-2026-58061 CVE-2026-58062 CVE-2026-58063 CVE-2026-59638 CVE-2026-59639 CVE-2026-59640 CVE-2026-59641 CVE-2026-59642 CVE-2026-59643 CVE-2026-59644 CVE-2026-59645 CVE-2026-59646 CVE-2026-59647 CVE-2026-59648 CVE-2026-59649 CVE-2026-59650 CVE-2026-59651 CVE-2026-59652 CVE-2026-8763 Message-ID: <178578430049.3531643.16106970676657353599.reportbug@eldamar.lan> X-Mailer: reportbug 13.2.0+nmu1 Date: Mon, 03 Aug 2026 21:11:40 +0200 Delivered-To: submit@bugs.debian.org Source: bouncycastle Version: 1.80-3 Severity: important Tags: security upstream X-Debbugs-Cc: carnil@debian.org, Debian Security Team <team@security.debian.org> Hi, The following vulnerabilities were published for bouncycastle. CVE-2026-12185[0]: | In Bouncy Castle for Java before 1.85, BKS/UBER keystore allocates | from untrusted lengths before integrity check. This issue also | affects Bouncy Castle for Java LTS before 2.73.12. CVE-2026-12802[1]: | In Bouncy Castle for Java before 1.85, CMS AuthEnvelopedData fails | to enforce tag-length on decryption. This issue also affects Bouncy | Castle for Java LTS before 2.73.12, and Bouncy Castle for Java FIPS | (BC-FJA) before bcpkix-fips 1.0.12 (1.0.X series), 2.0.12 (2.0.X | series) and 2.1.12 (2.1.X series). CVE-2026-12803[2]: | In Bouncy Castle for Java before 1.85, KCCMBlockCipher MAC does not | bind nonce when AAD is absent (cross-nonce AEAD forgery). This issue | also affects Bouncy Castle for Java LTS before 2.73.12. CVE-2026-12816[3]: | In Bouncy Castle for Java before 1.85, IESEngine stream-mode MAC | forgery via length-dependent KDF split. This issue also affects | Bouncy Castle for Java LTS before 2.73.12. CVE-2026-12817[4]: | In Bouncy Castle for Java before 1.85, OpenPGP AEAD decryption skips | final tag on chunk-aligned data. This issue also affects Bouncy | Castle for Java LTS before 2.73.12, and Bouncy Castle for Java FIPS | (BC-FJA) before bcpg-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-12852[5]: | In Bouncy Castle for Java before 1.85, MLS wire decoder allocates | attacker-declared opaque length before bounds check. CVE-2026-12860[6]: | In Bouncy Castle for Java before 1.85, RSA PKCS#1 verification skips | last two hash bytes in NULL-omitted path. This issue also affects | Bouncy Castle for Java LTS before 2.73.12. CVE-2026-13506[7]: | In Bouncy Castle for Java before 1.85, Lazy ASN.1 sequence forcing | resets nesting-depth guard. This issue also affects Bouncy Castle | for Java LTS before 2.73.12, and Bouncy Castle for Java FIPS (BC- | FJA) before bc-fips 1.0.2.7 (1.0.X series), 2.0.2 (2.0.X series) and | 2.1.3 (2.1.X series). CVE-2026-13586[8]: | In Bouncy Castle for Java before 1.85, PKCS#12 MAC and bag- | decryption KDF iteration-count bound (DoS). This issue also affects | Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle for | Java FIPS (BC-FJA) before bc-fips 1.0.2.7 (1.0.X series), 2.0.2 | (2.0.X series) and 2.1.3 (2.1.X series). CVE-2026-14682[9]: | In Bouncy Castle for Java before 1.85, Possible OOM from unbounded | up-front allocation on a definite-length read. This issue also | affects Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle | for Java FIPS (BC-FJA) before bc-fips 1.0.2.7 (1.0.X series), 2.0.2 | (2.0.X series) and 2.1.3 (2.1.X series), and before bctls-fips | 1.0.24. CVE-2026-15055[10]: | In Bouncy Castle for Java before 1.85, PKCS#8 / PBES2 decryptors | honour unbounded KDF cost from input. This issue also affects Bouncy | Castle for Java LTS before 2.73.12, and Bouncy Castle for Java FIPS | (BC-FJA) before bcpkix-fips 1.0.12 (1.0.X series), 2.0.12 (2.0.X | series) and 2.1.12 (2.1.X series). CVE-2026-58059[11]: | In Bouncy Castle for Java before 1.85, Quadratic-time escaping when | stringifying X.500 distinguished names. This issue also affects | Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle for | Java FIPS (BC-FJA) before bc-fips 1.0.2.7 (1.0.X series), 2.0.2 | (2.0.X series) and 2.1.3 (2.1.X series). CVE-2026-58060[12]: | In Bouncy Castle for Java before 1.85, HSS public-key level count | unbounded, enabling huge allocation on verify. This issue also | affects Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle | for Java FIPS (BC-FJA) before bc-fips 2.0.2 (2.0.X series) and 2.1.3 | (2.1.X series). CVE-2026-58061[13]: | In Bouncy Castle for Java before 1.85, CCM-family modes write | plaintext to caller buffer before tag check. This issue also affects | Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle for | Java FIPS (BC-FJA) before bc-fips 1.0.2.7 (1.0.X series), 2.0.2 | (2.0.X series) and 2.1.3 (2.1.X series). CVE-2026-58062[14]: | In Bouncy Castle for Java before 1.85, Stapled OCSP response | accepted without binding to the checked certificate. This issue also | affects Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle | for Java FIPS (BC-FJA) before bc-fips 2.0.2 (2.0.X series) and 2.1.3 | (2.1.X series). CVE-2026-58063[15]: | In Bouncy Castle for Java before 1.85, BCFKS keystore load honours | unbounded KDF cost from untrusted file. This issue also affects | Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle for | Java FIPS (BC-FJA) before bc-fips 1.0.2.7 (1.0.X series), 2.0.2 | (2.0.X series) and 2.1.3 (2.1.X series). CVE-2026-59638[16]: | In Bouncy Castle for Java before 1.85, JSSE hostname verifier CN- | fallback enabled by default despite documented opt-in. This issue | also affects Bouncy Castle for Java LTS before 2.73.12, and Bouncy | Castle for Java FIPS (BC-FJA) before bctls-fips 1.0.24 (1.0.X | series), 2.0.24 (2.0.X series) and 2.1.24 (2.1.X series). CVE-2026-59639[17]: | In Bouncy Castle for Java before 1.85, CMS verifySignatures returns | true for SignedData with zero signers. This issue also affects | Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle for | Java FIPS (BC-FJA) before bcpkix-fips 1.0.12 (1.0.X series), 2.0.12 | (2.0.X series) and 2.1.12 (2.1.X series). CVE-2026-59640[18]: | In Bouncy Castle for Java before 1.85, OpenPGP CFB quick-check | oracle active on symmetric/session-key paths. This issue also | affects Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle | for Java FIPS (BC-FJA) before bcpg-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-59641[19]: | In Bouncy Castle for Java before 1.85, S/MIME validator trusts | signer-asserted signingTime for path validation. This issue also | affects Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle | for Java FIPS (BC-FJA) before bcmail-fips and bcjmail-fips 1.0.7 | (1.0.X series), 2.0.7 (2.0.X series) and 2.1.7 (2.1.X series). CVE-2026-59642[20]: | In Bouncy Castle for Java before 1.85, CMS AuthenticatedData content | not bound to MAC when authAttrs present. This issue also affects | Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle for | Java FIPS (BC-FJA) before bcpkix-fips 1.0.12 (1.0.X series), 2.0.12 | (2.0.X series) and 2.1.12 (2.1.X series). CVE-2026-59643[21]: | In Bouncy Castle for Java before 1.85, OpenPGP inline-signature | policy failures silently ignored. This issue also affects Bouncy | Castle for Java FIPS (BC-FJA) before bcpg-fips 2.0.13. CVE-2026-59644[22]: | In Bouncy Castle for Java before 1.85, MLS hash-ratchet honours | arbitrary 32-bit generation counter from sender. CVE-2026-59645[23]: | In Bouncy Castle for Java before 1.85, OER parser recurses without | depth limit on self-referential IEEE 1609.2 schema. This issue also | affects Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle | for Java FIPS (BC-FJA) before bcutil-fips 2.0.7 (2.0.X series) and | 2.1.7 (2.1.X series). CVE-2026-59646[24]: | In Bouncy Castle for Java before 1.85, DTLS handshake reassembler | allocates buffer from unchecked 24-bit length. This issue also | affects Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle | for Java FIPS (BC-FJA) before bctls-fips 1.0.24 (1.0.X series), | 2.0.24 (2.0.X series) and 2.1.24 (2.1.X series). CVE-2026-59647[25]: | In Bouncy Castle for Java before 1.85, CRMF/CMP password-MAC honours | unbounded iteration count. This issue also affects Bouncy Castle for | Java LTS before 2.73.12, and Bouncy Castle for Java FIPS (BC-FJA) | before bcpkix-fips 1.0.12 (1.0.X series), 2.0.12 (2.0.X series) and | 2.1.12 (2.1.X series). CVE-2026-59648[26]: | In Bouncy Castle for Java before 1.85, OpenPGP Argon2 S2K honours | attacker-chosen memory and passes. This issue also affects Bouncy | Castle for Java LTS before 2.73.12, and Bouncy Castle for Java FIPS | (BC-FJA) before bcpg-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-59649[27]: | In Bouncy Castle for Java before 1.85, OpenPGP user-attribute | subpacket length bounded only by JVM max memory. This issue also | affects Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle | for Java FIPS (BC-FJA) before bcpg-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-59650[28]: | In Bouncy Castle for Java before 1.85, MTI/A0 DH agreement | exponentiates unvalidated peer value. This issue also affects Bouncy | Castle for Java LTS before 2.73.12. CVE-2026-59651[29]: | In Bouncy Castle for Java before 1.85, BKS keystore accepts legacy | version with 16-bit integrity MAC key. This issue also affects | Bouncy Castle for Java LTS before 2.73.12. CVE-2026-59652[30]: | In Bouncy Castle for Java before 1.85, LDAP filter injection in | legacy jdk1.4 LDAPStoreHelper. CVE-2026-8763[31]: | In Bouncy Castle for Java before 1.85, Name Constraints bypass via | trailing dot in rfc822Name and URI. This issue also affects Bouncy | Castle for Java LTS before 2.73.12, and Bouncy Castle for Java FIPS | (BC-FJA) before bc-fips 1.0.2.7 (1.0.X series), 2.0.2 (2.0.X series) | and 2.1.3 (2.1.X series). All of those are fixed in upstream r1rv85. If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2026-12185 https://www.cve.org/CVERecord?id=CVE-2026-12185 [1] https://security-tracker.debian.org/tracker/CVE-2026-12802 https://www.cve.org/CVERecord?id=CVE-2026-12802 [2] https://security-tracker.debian.org/tracker/CVE-2026-12803 https://www.cve.org/CVERecord?id=CVE-2026-12803 [3] https://security-tracker.debian.org/tracker/CVE-2026-12816 https://www.cve.org/CVERecord?id=CVE-2026-12816 [4] https://security-tracker.debian.org/tracker/CVE-2026-12817 https://www.cve.org/CVERecord?id=CVE-2026-12817 [5] https://security-tracker.debian.org/tracker/CVE-2026-12852 https://www.cve.org/CVERecord?id=CVE-2026-12852 [6] https://security-tracker.debian.org/tracker/CVE-2026-12860 https://www.cve.org/CVERecord?id=CVE-2026-12860 [7] https://security-tracker.debian.org/tracker/CVE-2026-13506 https://www.cve.org/CVERecord?id=CVE-2026-13506 [8] https://security-tracker.debian.org/tracker/CVE-2026-13586 https://www.cve.org/CVERecord?id=CVE-2026-13586 [9] https://security-tracker.debian.org/tracker/CVE-2026-14682 https://www.cve.org/CVERecord?id=CVE-2026-14682 [10] https://security-tracker.debian.org/tracker/CVE-2026-15055 https://www.cve.org/CVERecord?id=CVE-2026-15055 [11] https://security-tracker.debian.org/tracker/CVE-2026-58059 https://www.cve.org/CVERecord?id=CVE-2026-58059 [12] https://security-tracker.debian.org/tracker/CVE-2026-58060 https://www.cve.org/CVERecord?id=CVE-2026-58060 [13] https://security-tracker.debian.org/tracker/CVE-2026-58061 https://www.cve.org/CVERecord?id=CVE-2026-58061 [14] https://security-tracker.debian.org/tracker/CVE-2026-58062 https://www.cve.org/CVERecord?id=CVE-2026-58062 [15] https://security-tracker.debian.org/tracker/CVE-2026-58063 https://www.cve.org/CVERecord?id=CVE-2026-58063 [16] https://security-tracker.debian.org/tracker/CVE-2026-59638 https://www.cve.org/CVERecord?id=CVE-2026-59638 [17] https://security-tracker.debian.org/tracker/CVE-2026-59639 https://www.cve.org/CVERecord?id=CVE-2026-59639 [18] https://security-tracker.debian.org/tracker/CVE-2026-59640 https://www.cve.org/CVERecord?id=CVE-2026-59640 [19] https://security-tracker.debian.org/tracker/CVE-2026-59641 https://www.cve.org/CVERecord?id=CVE-2026-59641 [20] https://security-tracker.debian.org/tracker/CVE-2026-59642 https://www.cve.org/CVERecord?id=CVE-2026-59642 [21] https://security-tracker.debian.org/tracker/CVE-2026-59643 https://www.cve.org/CVERecord?id=CVE-2026-59643 [22] https://security-tracker.debian.org/tracker/CVE-2026-59644 https://www.cve.org/CVERecord?id=CVE-2026-59644 [23] https://security-tracker.debian.org/tracker/CVE-2026-59645 https://www.cve.org/CVERecord?id=CVE-2026-59645 [24] https://security-tracker.debian.org/tracker/CVE-2026-59646 https://www.cve.org/CVERecord?id=CVE-2026-59646 [25] https://security-tracker.debian.org/tracker/CVE-2026-59647 https://www.cve.org/CVERecord?id=CVE-2026-59647 [26] https://security-tracker.debian.org/tracker/CVE-2026-59648 https://www.cve.org/CVERecord?id=CVE-2026-59648 [27] https://security-tracker.debian.org/tracker/CVE-2026-59649 https://www.cve.org/CVERecord?id=CVE-2026-59649 [28] https://security-tracker.debian.org/tracker/CVE-2026-59650 https://www.cve.org/CVERecord?id=CVE-2026-59650 [29] https://security-tracker.debian.org/tracker/CVE-2026-59651 https://www.cve.org/CVERecord?id=CVE-2026-59651 [30] https://security-tracker.debian.org/tracker/CVE-2026-59652 https://www.cve.org/CVERecord?id=CVE-2026-59652 [31] https://security-tracker.debian.org/tracker/CVE-2026-8763 https://www.cve.org/CVERecord?id=CVE-2026-8763 Regards, Salvatore ]