Quick answers
- Is CVE-2026-63568 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-63568 being exploited in the wild.
- How severe is CVE-2026-63568?
- Informational severity, published 2 October 2026.
- Which products and versions are affected?
- Legion of the Bouncy Castle BouncyCastle.Cryptography before 2.7.0.
- Is there a fix for CVE-2026-63568?
- Yes: fixed in BouncyCastle.Cryptography 2.7.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-63568 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-63568?
- Check whether you run Legion of the Bouncy Castle BouncyCastle.Cryptography at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: BouncyCastle.Cryptography 2.7.0
Technical details
The PKMacBuilder component in Bouncy Castle's CMP/CRMF password-based MAC verifier lacks iteration-count enforcement by default. An attacker can craft a CMP message or CRMF certificate request with a PBMParameter declaring an extremely large iteration count (up to ~2^31), forcing ProtectedPkiMessage.Verify and CertificateRequestMessage.IsValidSigningKeyPop to perform that many hash iterations before validating the MAC, causing CPU exhaustion. The vulnerability only affects code paths not explicitly setting an iteration-count ceiling via the PKMacBuilder(IPKMacPrimitivesProvider, int) constructor.
Affected products
- Legion of the Bouncy Castle BouncyCastle.Cryptography before 2.7.0
Timeline
- 2026-10-02: disclosed