Loop with unreachable exit condition in Pkcs12Store.GetCertificateChain in Legion of the Bouncy Castle Inc. bc-csharp before 2.7.0 allows an attacker who can supply a crafted PKCS#12 file to an application that loads it and requests a key entry's certificate chain to cause a denial of service, in which the call never returns and consumes CPU and memory until an OutOfMemoryException, via certificates whose issuer links form a cycle, for example two certificates whose AuthorityKeyIdentifier extensions each identify the other's public key. This happens because the chain-building loop stops only when no issuer is found or a certificate links to itself, and keeps no record of certificates already visited. The key-identifier links are followed without checking signatures.
CVE-2026-63570
This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (10th 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
- 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.2%
- EPSS %ILE
- 10th
- 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 (2)
Auto-updated Oct 2, 2026commit 1b8fad04df49 (bcgit/bc-csharp)
Fix landed in bcgit/bc-csharp commit 1b8fad04df49 — awaiting tagged release
https://github.com/bcgit/bc-csharp/commit/1b8fad04df4953230c9951c57678ee45c8aead85CVE 2026 63570 · bcgit/bc-csharp Wiki · GitHub
https://github.com/bcgit/bc-csharp/wiki/CVE-2026-63570Vendor Advisories for CVE-2026-63570(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:12 UTCGHSA enrichment
- 2026-10-03 22:17 UTCEG score recompute
- 2026-10-03 22:16 UTCGHSA enrichment
- 2026-10-03 14:26 UTCEPSS rescore
- 2026-10-03 09:19 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-63570?
When was CVE-2026-63570 disclosed?
Is CVE-2026-63570 actively exploited?
What is the CVSS score of CVE-2026-63570?
How do I remediate CVE-2026-63570?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-63570
Is Your Infrastructure Affected by CVE-2026-63570?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.