Allocation of resources without limits in password-based private-key decryption (PbeUtilities.GenerateCipherParameters) in Legion of the Bouncy Castle Inc. bc-csharp before 2.7.0 allows an attacker who can supply an encrypted private key, such as a PKCS#8 EncryptedPrivateKeyInfo or "ENCRYPTED PRIVATE KEY" PEM file, to cause a denial of service through CPU exhaustion via an iteration count close to 2^31, because the count is taken from the unauthenticated algorithm parameters without an upper bound and the key derivation runs before the password or the data can be checked. PKCS#5 PBES1 and PBES2 (PBKDF2), the PKCS#12 PBE algorithms and CMS password recipients (CmsPbeKey) are affected. Loading PKCS#12 files with Pkcs12Store is covered by CVE-2026-63572, and a zero or negative count with the PKCS#12 algorithms by CVE-2026-63575.
CVE-2026-63578
This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (23rd percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.
- CVSS v3
- 7.1
- EG Score
- 7.1HIGHmedium confidence
- EG Risk
- 37EG Risk 37/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity71% × 45%Exploitation0% × 40%Automatability30% × 15%CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release. - EPSS PROB
- 0.3%
- EPSS %ILE
- 23rd
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).
An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.
Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
October 2, 2026
Last Modified
October 2, 2026
Advisory Details (6)
Auto-updated Oct 2, 2026commit b57165ecb779 (bcgit/bc-csharp)
Fix landed in bcgit/bc-csharp commit b57165ecb779 — awaiting tagged release
https://github.com/bcgit/bc-csharp/commit/b57165ecb7790ecea08273b219d52d80c12990e4commit 34a7c05f719c (bcgit/bc-csharp)
Fix landed in bcgit/bc-csharp commit 34a7c05f719c — awaiting tagged release
https://github.com/bcgit/bc-csharp/commit/34a7c05f719c91c024f285c6b420d3c00f8019ddcommit 7c0ed15f9783 (bcgit/bc-csharp)
Fix landed in bcgit/bc-csharp commit 7c0ed15f9783 — awaiting tagged release
https://github.com/bcgit/bc-csharp/commit/7c0ed15f9783c9595b1a53f3900136461fd944f4commit 54ea0b179ee6 (bcgit/bc-csharp)
Fix landed in bcgit/bc-csharp commit 54ea0b179ee6 — awaiting tagged release
https://github.com/bcgit/bc-csharp/commit/54ea0b179ee627027829b44c45d6dd32e575bd67commit c00fc018fca8 (bcgit/bc-csharp)
Fix landed in bcgit/bc-csharp commit c00fc018fca8 — awaiting tagged release
https://github.com/bcgit/bc-csharp/commit/c00fc018fca89c077c64dd2a2a2eb00ae7d97241CVE 2026 63578 · bcgit/bc-csharp Wiki · GitHub
https://github.com/bcgit/bc-csharp/wiki/CVE-2026-63578Vendor Advisories for CVE-2026-63578(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 11× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-04 03:22 UTCGHSA enrichment
- 2026-10-03 15:10 UTCEG score recompute
- 2026-10-03 15:10 UTCGHSA enrichment
- 2026-10-03 14:26 UTCEPSS rescore
- 2026-10-03 02:58 UTCEG score recompute
- 2026-10-03 02:58 UTCGHSA enrichment
- 2026-10-02 17:56 UTCEPSS rescore
- 2026-10-02 14:45 UTCGHSA enrichment
- 2026-10-02 08:27 UTCEG score recompute
- 2026-10-02 07:31 UTCEG score recompute
- 2026-10-02 07:30 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-63578?
When was CVE-2026-63578 disclosed?
Is CVE-2026-63578 actively exploited?
What is the CVSS score of CVE-2026-63578?
How do I remediate CVE-2026-63578?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-63578
Is Your Infrastructure Affected by CVE-2026-63578?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.