CVE-2026-8763

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

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, ghsa, nvd
9.1EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.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.

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/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
Severity91% × 45%
Exploitation0% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; 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.4%
EPSS %ILE
35th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; 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 (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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

August 3, 2026

Last Modified

October 5, 2026

Advisory Details (3)

Auto-updated Sep 15, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

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
generic

Home · bcgit/bc-java Wiki · GitHub

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

Vendor Advisories for CVE-2026-8763(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

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.

Data Freshness Timeline

(refreshed 11× in last 7d / 105× 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.

Showing the most recent 100 of 363 total refreshes for this CVE.

  1. 2026-10-04 23:47 UTCEG score recompute
  2. 2026-10-04 23:22 UTCEPSS rescore
  3. 2026-10-04 06:23 UTCEG score recompute
  4. 2026-10-03 02:40 UTCEG score recompute
  5. 2026-10-02 10:26 UTCEG score recompute
  6. 2026-10-01 19:51 UTCEPSS rescore
  7. 2026-10-01 02:40 UTCEG score recompute
  8. 2026-09-30 15:04 UTCEPSS rescore
  9. 2026-09-29 06:45 UTCEG score recompute
  10. 2026-09-28 13:52 UTCEPSS rescore
  11. 2026-09-28 13:52 UTCEPSS rescore
  12. 2026-09-27 18:19 UTCEG score recompute
  13. 2026-09-27 13:49 UTCEPSS rescore
  14. 2026-09-26 15:59 UTCEPSS rescore
  15. 2026-09-25 04:49 UTCEG score recompute
  16. 2026-09-24 14:04 UTCEPSS rescore
  17. 2026-09-23 21:25 UTCEG score recompute
  18. 2026-09-23 17:54 UTCEPSS rescore
  19. 2026-09-22 21:30 UTCEG score recompute
  20. 2026-09-22 16:01 UTCEPSS rescore
  21. 2026-09-22 06:43 UTCEG score recompute
  22. 2026-09-21 21:09 UTCEPSS rescore
  23. 2026-09-20 20:58 UTCEG score recompute
  24. 2026-09-20 20:16 UTCEPSS rescore
  25. 2026-09-19 17:59 UTCEG score recompute
Show 75 more
  1. 2026-09-18 22:24 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 13:20 UTCGHSA enrichment
  4. 2026-09-18 08:38 UTCGHSA enrichment
  5. 2026-09-18 04:55 UTCGHSA enrichment
  6. 2026-09-18 01:13 UTCEG score recompute
  7. 2026-09-18 01:13 UTCGHSA enrichment
  8. 2026-09-17 19:32 UTCEPSS rescore
  9. 2026-09-17 08:44 UTCGHSA enrichment
  10. 2026-09-17 05:00 UTCGHSA enrichment
  11. 2026-09-17 01:17 UTCEG score recompute
  12. 2026-09-17 01:17 UTCGHSA enrichment
  13. 2026-09-16 14:09 UTCEPSS rescore
  14. 2026-09-16 11:18 UTCGHSA enrichment
  15. 2026-09-16 05:20 UTCEG score recompute
  16. 2026-09-16 05:20 UTCGHSA enrichment
  17. 2026-09-16 05:15 UTCEPSS rescore
  18. 2026-09-15 17:09 UTCGHSA enrichment
  19. 2026-09-15 07:04 UTCEG score recompute
  20. 2026-09-15 07:04 UTCGHSA enrichment
  21. 2026-09-15 03:12 UTCEPSS rescore
  22. 2026-09-15 02:06 UTCGHSA enrichment
  23. 2026-09-14 16:59 UTCGHSA enrichment
  24. 2026-09-14 13:17 UTCGHSA enrichment
  25. 2026-09-14 09:05 UTCGHSA enrichment
  26. 2026-09-14 05:23 UTCGHSA enrichment
  27. 2026-09-14 01:40 UTCGHSA enrichment
  28. 2026-09-13 21:57 UTCGHSA enrichment
  29. 2026-09-13 18:14 UTCEG score recompute
  30. 2026-09-13 18:14 UTCGHSA enrichment
  31. 2026-09-13 16:48 UTCEPSS rescore
  32. 2026-09-13 14:31 UTCGHSA enrichment
  33. 2026-09-13 10:49 UTCGHSA enrichment
  34. 2026-09-13 07:07 UTCGHSA enrichment
  35. 2026-09-13 03:25 UTCGHSA enrichment
  36. 2026-09-12 23:42 UTCGHSA enrichment
  37. 2026-09-12 19:43 UTCGHSA enrichment
  38. 2026-09-12 16:01 UTCEG score recompute
  39. 2026-09-12 16:01 UTCGHSA enrichment
  40. 2026-09-12 15:02 UTCEPSS rescore
  41. 2026-09-12 12:18 UTCGHSA enrichment
  42. 2026-09-12 08:21 UTCGHSA enrichment
  43. 2026-09-12 04:15 UTCGHSA enrichment
  44. 2026-09-12 00:29 UTCGHSA enrichment
  45. 2026-09-11 18:36 UTCGHSA enrichment
  46. 2026-09-11 14:54 UTCEG score recompute
  47. 2026-09-11 14:54 UTCGHSA enrichment
  48. 2026-09-11 14:53 UTCEPSS rescore
  49. 2026-09-11 09:52 UTCEG score recompute
  50. 2026-09-11 09:51 UTCGHSA enrichment
  51. 2026-09-11 09:38 UTCEPSS rescore
  52. 2026-09-11 06:01 UTCGHSA enrichment
  53. 2026-09-11 02:11 UTCGHSA enrichment
  54. 2026-09-10 22:28 UTCGHSA enrichment
  55. 2026-09-10 18:46 UTCGHSA enrichment
  56. 2026-09-10 12:53 UTCEG score recompute
  57. 2026-09-10 12:53 UTCGHSA enrichment
  58. 2026-09-10 06:57 UTCGHSA enrichment
  59. 2026-09-10 03:14 UTCGHSA enrichment
  60. 2026-09-09 19:42 UTCGHSA enrichment
  61. 2026-09-09 10:49 UTCGHSA enrichment
  62. 2026-09-09 06:53 UTCEG score recompute
  63. 2026-09-09 06:52 UTCGHSA enrichment
  64. 2026-09-08 22:01 UTCEPSS rescore
  65. 2026-09-08 02:31 UTCGHSA enrichment
  66. 2026-09-07 22:48 UTCGHSA enrichment
  67. 2026-09-07 19:05 UTCEG score recompute
  68. 2026-09-07 19:05 UTCGHSA enrichment
  69. 2026-09-06 20:43 UTCGHSA enrichment
  70. 2026-09-06 16:58 UTCEG score recompute
  71. 2026-09-06 16:58 UTCGHSA enrichment
  72. 2026-09-06 13:48 UTCEPSS rescore
  73. 2026-09-06 13:15 UTCGHSA enrichment
  74. 2026-09-06 09:33 UTCGHSA enrichment
  75. 2026-09-06 05:51 UTCGHSA enrichment

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-8763?
CVE-2026-8763 is a critical vulnerability 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 CVE-2026-8763 disclosed?
CVE-2026-8763 was first published on August 3, 2026, with the most recent update on October 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
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 (35th 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?
An upstream fix for CVE-2026-8763 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-8763 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs