Allocation of resources without limits in PKCS#12 keystore loading (Pkcs12Store.Load) in Legion of the Bouncy Castle Inc. bc-csharp before 2.7.0 allows an attacker who can supply a PKCS#12 (PFX) file to cause a denial of service through CPU exhaustion via an iteration count close to 2^31 in the file's MacData or in the PBE parameters of an encrypted SafeContents or shrouded key bag, because the counts are taken from the file without an upper bound and the key derivation runs before the MAC or the password can be checked. A zero or negative count is covered by CVE-2026-63575. Pkcs12Utilities.ConvertToDefiniteLength is also affected.
CVE-2026-63572
HIGHPre-NVD 7.17.1—Trending — 4 sources updated this week
EchelonGraph scoreMEDIUM confidence
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).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.1EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.1Exploit: None knownExposed services: Not assessed
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
- 32EG Risk 32/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%Automatability0% × 15%CISA SSVC: Track at every mission impact level.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 until it ships, then apply the release. - EPSS PROB
- 0.3%
- EPSS %ILE
- 23rd
- KEV
- Not listed
CISA SSVCTrack at every mission impact level.
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 until it ships, then apply the release.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). 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, 2026Upstream fix merged — awaiting tagged release. Sources: github_commit.
github_commit
commit b57165ecb779 (bcgit/bc-csharp)
Fix landed in bcgit/bc-csharp commit b57165ecb779 — awaiting tagged release
https://github.com/bcgit/bc-csharp/commit/b57165ecb7790ecea08273b219d52d80c12990e4github_commit
commit 34a7c05f719c (bcgit/bc-csharp)
Fix landed in bcgit/bc-csharp commit 34a7c05f719c — awaiting tagged release
https://github.com/bcgit/bc-csharp/commit/34a7c05f719c91c024f285c6b420d3c00f8019ddgithub_commit
commit 54ea0b179ee6 (bcgit/bc-csharp)
Fix landed in bcgit/bc-csharp commit 54ea0b179ee6 — awaiting tagged release
https://github.com/bcgit/bc-csharp/commit/54ea0b179ee627027829b44c45d6dd32e575bd67github_commit
commit c00fc018fca8 (bcgit/bc-csharp)
Fix landed in bcgit/bc-csharp commit c00fc018fca8 — awaiting tagged release
https://github.com/bcgit/bc-csharp/commit/c00fc018fca89c077c64dd2a2a2eb00ae7d97241github_commit
commit 7c0ed15f9783 (bcgit/bc-csharp)
Fix landed in bcgit/bc-csharp commit 7c0ed15f9783 — awaiting tagged release
https://github.com/bcgit/bc-csharp/commit/7c0ed15f9783c9595b1a53f3900136461fd944f4generic
CVE 2026 63572 · bcgit/bc-csharp Wiki · GitHub
https://github.com/bcgit/bc-csharp/wiki/CVE-2026-63572Vendor Advisories for CVE-2026-63572(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 14× in last 7d / 14× 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 11:42 UTCGHSA enrichment
- 2026-10-03 22:36 UTCEG score recompute
- 2026-10-03 22:35 UTCGHSA enrichment
- 2026-10-03 14:26 UTCEPSS rescore
- 2026-10-03 09:28 UTCGHSA enrichment
- 2026-10-02 20:20 UTCEG score recompute
- 2026-10-02 20:20 UTCGHSA enrichment
- 2026-10-02 19:26 UTCEG score recompute
- 2026-10-02 19:26 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-63572?
CVE-2026-63572 is a high vulnerability published on October 2, 2026. Allocation of resources without limits in PKCS#12 keystore loading (Pkcs12Store.Load) in Legion of the Bouncy Castle Inc. bc-csharp before 2.7.0 allows an attacker who can supply a PKCS#12 (PFX) file to cause a denial of service through CPU exhaustion via an iteration count close to 2^31 in the…
When was CVE-2026-63572 disclosed?
CVE-2026-63572 was first published on October 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63572 actively exploited?
CVE-2026-63572 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-63572?
CVE-2026-63572 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-63572?
An upstream fix for CVE-2026-63572 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-63572 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-63572
Is Your Infrastructure Affected by CVE-2026-63572?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.