Allocation of Resources Without Limits or Throttling Affecting bouncycastle.cryptography package, versions [,2.7.0)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Allocation of Resources Without Limits or Throttling vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-DOTNET-BOUNCYCASTLECRYPTOGRAPHY-20537018
- published6 Oct 2026
- disclosed2 Oct 2026
Introduced: 2 Oct 2026
NewCVE-2026-63578 (opens in a new tab)How to fix?
Upgrade BouncyCastle.Cryptography to version 2.7.0 or higher.
Overview
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in PbeUtilities.GenerateCipherParameters for encrypted PKCS#8 private keys. An attacker can exhaust CPU by supplying a malicious EncryptedPrivateKeyInfo or ENCRYPTED PRIVATE KEY PEM file with an extremely large unauthenticated PBE iteration count, causing the key derivation to run for an excessive number of iterations before the password or ciphertext can be rejected. This affects PKCS#5 PBES1 and PBES2/PBKDF2 private-key imports and can stall applications or services that load attacker-controlled encrypted keys.
Workarounds
- Restrict the system so untrusted users cannot supply encrypted PKCS#8 /
ENCRYPTED PRIVATE KEYfiles or other attacker-controlled password-based private keys to the component that decrypts them; this prevents CPU exhaustion from maliciously large PBE iteration counts during import.