CVE-2026-58062

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-52089 (ENISA EUVD) · GHSA-j295-77c3-9frf (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, Stapled OCSP response accepted without binding to the checked certificate. This issue also affects Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle for Java FIPS (BC-FJA) before bc-fips 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
30th
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

September 2, 2026

Advisory Details (3)

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

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

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

commit add5f822660f (bcgit/bc-java)

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

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

Home · bcgit/bc-java Wiki · GitHub

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

Patch Availability(16)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-modelmesh-rhel9:17933407462026-11-19redhat
oraclepatch2026-11-17oracle
redhatbcpkix-jdk18on2026-11-06redhat
redhatdevspaces/pluginregistry-rhel9:17924952122026-10-26redhat
redhatocp-tools-4/jenkins-rhel9:17920415142026-10-22redhat
redhatocp-tools-4/jenkins-rhel8:17920443272026-10-22redhat
redhatocp-tools-4/jenkins-rhel8:17920443862026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920402872026-10-22redhat
redhatocp-tools-4/jenkins-rhel8:17920443262026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920407332026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920404282026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920400812026-10-22redhat
redhatocp-tools-4/jenkins-rhel8:17920443822026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920400962026-10-22redhat
redhatocp-tools-4/jenkins-rhel9:17920401312026-10-22redhat
oraclepatch2026-10-20oracle

These rows come from Red Hat and Oracle. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
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 22× in last 7d / 90× 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 553 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 453 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-58062?
CVE-2026-58062 is a critical-severity vulnerability; its CVE record was published on August 3, 2026. In Bouncy Castle for Java before 1.85, Stapled OCSP response accepted without binding to the checked certificate. This issue also affects Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle for Java FIPS (BC-FJA) before bc-fips 2.0.2 (2.0.X series) and 2.1.3 (2.1.X series).
When was the CVE record for CVE-2026-58062 published?
The CVE record for CVE-2026-58062 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 September 2, 2026; the record at its source may have been updated since.
Is CVE-2026-58062 actively exploited?
CVE-2026-58062 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-58062?
CVE-2026-58062 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-58062?
A fix for CVE-2026-58062 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-58062 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-58062

Explore →

Is Your Infrastructure Affected by CVE-2026-58062?

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