CVE-2026-63576

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (11th 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
Trending — 4 sources updated this week
8.2EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 8.2Exploit: 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.

Improper certificate validation in PkixNameConstraintValidator (ExtractHostFromURL) in Legion of the Bouncy Castle Inc. bc-csharp before 2.7.0 allows a name-constrained subordinate CA, or anyone able to obtain certificates with chosen subjectAltName URIs from such a CA, to bypass permitted or excluded uniformResourceIdentifier name constraints during certification path validation via a URI whose path, query, fragment or userinfo contains characters such as '@' or ':', because the host was extracted by string slicing without first isolating the RFC 3986 authority component, so the host compared against the constraints could differ from the URI's actual host.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
41
EG Risk 41/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 computed
Severity82% × 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.2%
EPSS %ILE
11th
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 (2)

Auto-updated Oct 2, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
github_commit

commit f196a22bbf77 (bcgit/bc-csharp)

Fix landed in bcgit/bc-csharp commit f196a22bbf77 — awaiting tagged release

https://github.com/bcgit/bc-csharp/commit/f196a22bbf7765cc19b0c4f4645c74ea7ad35e09
generic

CVE 2026 63576 · bcgit/bc-csharp Wiki · GitHub

https://github.com/bcgit/bc-csharp/wiki/CVE-2026-63576

Vendor Advisories for CVE-2026-63576(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.

  1. 2026-10-04 00:01 UTCEG score recompute
  2. 2026-10-04 00:01 UTCGHSA enrichment
  3. 2026-10-03 14:26 UTCEPSS rescore
  4. 2026-10-03 12:55 UTCGHSA enrichment
  5. 2026-10-03 01:50 UTCEG score recompute
  6. 2026-10-03 01:50 UTCGHSA enrichment
  7. 2026-10-02 17:56 UTCEPSS rescore
  8. 2026-10-02 14:45 UTCGHSA enrichment
  9. 2026-10-02 08:27 UTCEG score recompute
  10. 2026-10-02 07:31 UTCEG score recompute
  11. 2026-10-02 07:30 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-63576?
CVE-2026-63576 is a high vulnerability published on October 2, 2026. Improper certificate validation in PkixNameConstraintValidator (ExtractHostFromURL) in Legion of the Bouncy Castle Inc. bc-csharp before 2.7.0 allows a name-constrained subordinate CA, or anyone able to obtain certificates with chosen subjectAltName URIs from such a CA, to bypass permitted or…
When was CVE-2026-63576 disclosed?
CVE-2026-63576 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-63576 actively exploited?
CVE-2026-63576 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-63576?
CVE-2026-63576 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-63576?
An upstream fix for CVE-2026-63576 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-63576 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-63576

Explore →

Is Your Infrastructure Affected by CVE-2026-63576?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.