CVE-2026-8763

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-03. NVD baseline CVSS 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — Patch released this week

Also known asEUVD-2026-52020 (ENISA EUVD) · GHSA-9pwp-9qqc-pr26 (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In Bouncy Castle for Java before 1.85, Name Constraints bypass via trailing dot in rfc822Name and URI. This issue also affects Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle for Java FIPS (BC-FJA) before bc-fips 1.0.2.7 (1.0.X series), 2.0.2 (2.0.X series) and 2.1.3 (2.1.X series).

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
56
EG Risk 56/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
37th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 3, 2026

Last Modified

October 5, 2026

Advisory Details (3)

Auto-updated Sep 15, 2026
Patch available. Sources: github_commit.
Web page

CVE‐2026‐8763 · bcgit/bc-java Wiki · GitHub

https://github.com/bcgit/bc-java/wiki/CVE%E2%80%902026%E2%80%908763
GitHub commit

commit 2c28b253a446 (bcgit/bc-java)

Fix landed in bcgit/bc-java commit 2c28b253a446 — awaiting tagged release

https://github.com/bcgit/bc-java/commit/2c28b253a44681fbbc562561eab6ad383d2ae558
Web page

Home · bcgit/bc-java Wiki · GitHub

https://github.com/bcgit/bc-java/wiki/CVE-2026-8763

Vendor and National Authority Advisories for CVE-2026-8763(9)

These vendors and national cybersecurity authorities published their own advisory mentioning this CVE — often with remediation steps + affected product lists not in NVD. An authority's is an excerpt, in the language it published it in, not translated, and credited to it with a link.

Patch Availability(13)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
oraclepatch2026-11-17oracle
redhatrhbk/keycloak-rhel9-operator:26.6-242026-11-06redhat
redhatbcpkix-jdk18on2026-11-06redhat
redhatrhbk/keycloak-rhel92026-11-06redhat
redhatrhbk/keycloak-rhel9-operator:26.4-302026-11-06redhat
oraclepatch2026-10-20oracle
oraclepatch2026-10-20oracle
oraclepatch2026-10-20oracle
mavenorg.bouncycastle:bc-fips @ 1.0.2.7 (fixes < 1.0.2.7)—ghsa
mavenorg.bouncycastle:bc-fips @ 2.0.2 (fixes >= 2.0.0, < 2.0.2)—ghsa
mavenorg.bouncycastle:bc-fips @ 2.1.3 (fixes >= 2.1.0, < 2.1.3)—ghsa
mavenorg.bouncycastle:bcprov-jdk15to18 @ 1.85 (fixes < 1.85)—ghsa
mavenorg.bouncycastle:bcprov-lts8on @ 2.73.12 (fixes < 2.73.12)—ghsa

These rows come from Oracle, Red Hat and GitHub (GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(8 across 5 ecosystems)
Maven(4)
PackageVulnerable rangeFix by version rangeDependents
org.bouncycastle:bc-fips2.1.0, 2.1.1, 2.1.2
  • every version up to 1.0.2.7: fixed in 1.0.2.7
  • 2.0.0 up to 2.0.2: fixed in 2.0.2
  • 2.1.0 up to 2.1.3: fixed in 2.1.3
—
org.bouncycastle:bcprov-jdk15to181.63 ... 1.84 (23 versions)
  • every version up to 1.85: fixed in 1.85
—
org.bouncycastle:bcprov-jdk18on1.71 ... 1.84 (18 versions)
  • every version up to 1.85: fixed in 1.85
—
org.bouncycastle:bcprov-lts8on2.73.0 ... 2.73.9 (12 versions)
  • every version up to 2.73.12: fixed in 2.73.12
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
bouncycastle1.68-2 ... 1.80-3 (12 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
bouncycastle1.72-2 ... 1.86-1 (6 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
bouncycastle1.80-3, 1.86-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
bouncycastle1.80-3
  • every version up to 1.86-1: fixed in 1.86-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 24× in last 7d / 71× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 500 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 400 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-22 13:02 UTCEchelonGraph re-scored
  2. 2026-11-22 13:02 UTCVendor advisory
  3. 2026-11-22 13:02 UTCGHSA enrichmentGHSA-9pwp-9qqc-pr26 · GitHub severity CRITICAL · GitHub CVSS 9.1
  4. 2026-11-22 06:39 UTCVendor advisory
  5. 2026-11-21 16:42 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  6. 2026-11-21 13:47 UTCEchelonGraph re-scored
  7. 2026-11-21 13:47 UTCVendor advisory
  8. 2026-11-21 13:47 UTCGHSA enrichmentGHSA-9pwp-9qqc-pr26 · GitHub severity CRITICAL · GitHub CVSS 9.1
  9. 2026-11-20 16:39 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  10. 2026-11-20 14:36 UTCEchelonGraph re-scored
  11. 2026-11-20 14:36 UTCVendor advisory
  12. 2026-11-20 14:36 UTCGHSA enrichmentGHSA-9pwp-9qqc-pr26 · GitHub severity CRITICAL · GitHub CVSS 9.1
  13. 2026-11-19 16:36 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  14. 2026-11-19 15:25 UTCEchelonGraph re-scored
  15. 2026-11-19 15:25 UTCVendor advisory
  16. 2026-11-19 15:25 UTCGHSA enrichmentGHSA-9pwp-9qqc-pr26 · GitHub severity CRITICAL · GitHub CVSS 9.1
  17. 2026-11-18 16:36 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  18. 2026-11-18 16:14 UTCVendor advisory
  19. 2026-11-18 16:14 UTCGHSA enrichmentGHSA-9pwp-9qqc-pr26 · GitHub severity CRITICAL · GitHub CVSS 9.1
  20. 2026-11-17 16:57 UTCEchelonGraph re-scored
  21. 2026-11-17 16:57 UTCVendor advisory
  22. 2026-11-17 16:57 UTCGHSA enrichmentGHSA-9pwp-9qqc-pr26 · GitHub severity CRITICAL · GitHub CVSS 9.1
  23. 2026-11-17 16:36 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  24. 2026-11-16 17:45 UTCEchelonGraph re-scored
  25. 2026-11-16 17:45 UTCVendor advisory
Show 75 more
  1. 2026-11-16 17:45 UTCGHSA enrichmentGHSA-9pwp-9qqc-pr26 · GitHub severity CRITICAL · GitHub CVSS 9.1
  2. 2026-11-16 16:53 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  3. 2026-11-15 18:32 UTCEchelonGraph re-scored
  4. 2026-11-15 18:32 UTCVendor advisory
  5. 2026-11-15 18:32 UTCGHSA enrichmentGHSA-9pwp-9qqc-pr26 · GitHub severity CRITICAL · GitHub CVSS 9.1
  6. 2026-11-15 17:03 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  7. 2026-11-14 19:08 UTCEchelonGraph re-scored
  8. 2026-11-14 19:08 UTCVendor advisory
  9. 2026-11-14 19:08 UTCGHSA enrichmentGHSA-9pwp-9qqc-pr26 · GitHub severity CRITICAL · GitHub CVSS 9.1
  10. 2026-11-14 16:42 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  11. 2026-11-13 19:53 UTCEchelonGraph re-scored
  12. 2026-11-13 19:53 UTCVendor advisory
  13. 2026-11-13 19:53 UTCGHSA enrichmentGHSA-9pwp-9qqc-pr26 · GitHub severity CRITICAL · GitHub CVSS 9.1
  14. 2026-11-13 16:58 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  15. 2026-11-12 19:23 UTCEchelonGraph re-scored
  16. 2026-11-12 19:23 UTCVendor advisory
  17. 2026-11-12 19:23 UTCGHSA enrichmentGHSA-9pwp-9qqc-pr26 · GitHub severity CRITICAL · GitHub CVSS 9.1
  18. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  19. 2026-11-11 20:11 UTCEchelonGraph re-scored
  20. 2026-11-11 20:11 UTCVendor advisory
  21. 2026-11-11 20:11 UTCGHSA enrichmentGHSA-9pwp-9qqc-pr26 · GitHub severity CRITICAL · GitHub CVSS 9.1
  22. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  23. 2026-11-10 20:59 UTCEchelonGraph re-scored
  24. 2026-11-10 20:59 UTCVendor advisory
  25. 2026-11-10 20:59 UTCGHSA enrichmentGHSA-9pwp-9qqc-pr26 · GitHub severity CRITICAL · GitHub CVSS 9.1
  26. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  27. 2026-11-09 21:25 UTCEchelonGraph re-scored
  28. 2026-11-09 21:25 UTCVendor advisory
  29. 2026-11-09 21:25 UTCGHSA enrichmentGHSA-9pwp-9qqc-pr26 · GitHub severity CRITICAL · GitHub CVSS 9.1
  30. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  31. 2026-11-08 22:14 UTCEchelonGraph re-scored
  32. 2026-11-08 22:14 UTCVendor advisory
  33. 2026-11-08 22:14 UTCGHSA enrichmentGHSA-9pwp-9qqc-pr26 · GitHub severity CRITICAL · GitHub CVSS 9.1
  34. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  35. 2026-11-07 22:58 UTCEchelonGraph re-scored
  36. 2026-11-07 22:58 UTCVendor advisory
  37. 2026-11-07 22:58 UTCGHSA enrichmentGHSA-9pwp-9qqc-pr26 · GitHub severity CRITICAL · GitHub CVSS 9.1
  38. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  39. 2026-11-06 23:44 UTCEchelonGraph re-scored
  40. 2026-11-06 23:44 UTCVendor advisory
  41. 2026-11-06 23:44 UTCGHSA enrichmentGHSA-9pwp-9qqc-pr26 · GitHub severity CRITICAL · GitHub CVSS 9.1
  42. 2026-11-06 20:55 UTCOSV refresh
  43. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  44. 2026-11-06 00:33 UTCEchelonGraph re-scored
  45. 2026-11-06 00:33 UTCGHSA enrichmentGHSA-9pwp-9qqc-pr26 · GitHub severity CRITICAL · GitHub CVSS 9.1
  46. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  47. 2026-11-05 01:22 UTCEchelonGraph re-scored
  48. 2026-11-05 01:22 UTCGHSA enrichmentGHSA-9pwp-9qqc-pr26 · GitHub severity CRITICAL · GitHub CVSS 9.1
  49. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  50. 2026-11-04 02:10 UTCEchelonGraph re-scored
  51. 2026-11-04 02:10 UTCGHSA enrichmentGHSA-9pwp-9qqc-pr26 · GitHub severity CRITICAL · GitHub CVSS 9.1
  52. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  53. 2026-11-03 02:58 UTCEchelonGraph re-scored
  54. 2026-11-03 02:58 UTCGHSA enrichmentGHSA-9pwp-9qqc-pr26 · GitHub severity CRITICAL · GitHub CVSS 9.1
  55. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  56. 2026-11-02 03:46 UTCEchelonGraph re-scored
  57. 2026-11-02 03:46 UTCGHSA enrichmentGHSA-9pwp-9qqc-pr26 · GitHub severity CRITICAL · GitHub CVSS 9.1
  58. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  59. 2026-11-01 04:35 UTCEchelonGraph re-scored
  60. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  61. 2026-10-31 05:24 UTCEchelonGraph re-scored
  62. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  63. 2026-10-30 06:12 UTCEchelonGraph re-scored
  64. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  65. 2026-10-29 07:01 UTCEchelonGraph re-scored
  66. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  67. 2026-10-28 07:49 UTCEchelonGraph re-scored
  68. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  69. 2026-10-27 08:37 UTCEchelonGraph re-scored
  70. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  71. 2026-10-26 07:25 UTCEchelonGraph re-scored
  72. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  73. 2026-10-25 13:54 UTCEchelonGraph re-scored
  74. 2026-10-25 08:14 UTCEchelonGraph re-scored
  75. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile

Frequently asked(5)

What is CVE-2026-8763?
CVE-2026-8763 is a critical-severity vulnerability; its CVE record was published on August 3, 2026. In Bouncy Castle for Java before 1.85, Name Constraints bypass via trailing dot in rfc822Name and URI. This issue also affects Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle for Java FIPS (BC-FJA) before bc-fips 1.0.2.7 (1.0.X series), 2.0.2 (2.0.X series) and 2.1.3 (2.1.X series).
When was the CVE record for CVE-2026-8763 published?
The CVE record for CVE-2026-8763 was published on August 3, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 5, 2026; the record at its source may have been updated since.
Is CVE-2026-8763 actively exploited?
CVE-2026-8763 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-8763?
CVE-2026-8763 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-8763?
A fix for CVE-2026-8763 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-8763 are linked in the Vendor and National Authority Advisories panel on this page. NCSC-NL's 3 advisories for CVE-2026-8763 are also listed there, in Dutch, as NCSC-NL published it; not translated.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-8763

Explore →

Is Your Infrastructure Affected by CVE-2026-8763?

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