CVE-2026-47058

HIGHPre-NVD 7.47.4
EchelonGraph scoreMEDIUM confidence

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

Score 7.4 from GitHub Security Advisory (severity: HIGH) published 2026-07-22. A secondary CVSS source baseline 7.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-46544 (ENISA EUVD) · GHSA-j75p-jh2f-6h9p (GitHub Security Advisories)Source: ENISA EUVD

7.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Vulnerability in Oracle Java SE (component: Scripting). Supported versions that are affected are Oracle Java SE: 8u491, 8u491-perf and 11.0.31. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Java SE accessible data as well as unauthorized access to critical data or complete access to all Oracle Java SE accessible data. Note: This vulnerability can be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. This vulnerability also applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. CVSS 3.1 Base Score 7.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N).

CVSS v3
7.4
EG Score
7.4HIGHmedium confidence
EG Risk
33
EG Risk 33/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)
Severity74% × 45%
Impact severity (EG Severity): CVSS 7.4 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.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.4%
EPSS %ILE
32nd
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 (7.4): severity, escalated by confirmed exploitation. This CVE's 7.4 is its impact severity (EG Severity), not escalated.

EG Severity
7.4 HIGHCVSS-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-10-24). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

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

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (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

July 21, 2026

Last Modified

October 24, 2026

References (1)

Vendor Advisories for CVE-2026-47058(9)

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

Patch Availability(10)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuopenjdk-8-source (8u502-ga~us1-0ubuntu1~20.04) @ focal2026-10-24ubuntu
ubuntuopenjdk-11-source (11.0.32+9-1ubuntu1~18.04) @ bionic2026-10-24ubuntu
redhatjava-1.8.0-ibm-1:1.8.0.8.70-1.el8_102026-08-10redhat
redhatjava-11-openjdk-windows2026-07-23redhat
redhatjava-11-openjdk-1:11.0.32.0.9-1.el92026-07-23redhat
redhatjava-11-openjdk-portable2026-07-23redhat
redhatjava-1.8.0-openjdk-portable2026-07-23redhat
redhatjava-1.8.0-openjdk-windows2026-07-23redhat
redhatjava-1.8.0-openjdk-1:1.8.0.502.b07-1.1.el7_92026-07-23redhat
redhatjava-1.8.0-openjdk-1:1.8.0.502.b07-1.1.el92026-07-23redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
openjdk-1111.0.12+7-2 ... 11.0.32~8ea-1 (72 versions)
  • every version up to 11.0.32+9-2~deb11u1: fixed in 11.0.32+9-2~deb11u1
—

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 11× in last 7d / 48× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 100 of 348 refreshes 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 248 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-47058?
CVE-2026-47058 is a high-severity vulnerability; its CVE record was published on July 21, 2026. Vulnerability in Oracle Java SE (component: Scripting). Supported versions that are affected are Oracle Java SE: 8u491, 8u491-perf and 11.0.31. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE. Successful…
When was the CVE record for CVE-2026-47058 published?
The CVE record for CVE-2026-47058 was published on July 21, 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 24, 2026; the record at its source may have been updated since.
Is CVE-2026-47058 actively exploited?
CVE-2026-47058 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-47058?
CVE-2026-47058 has a CVSS base score of 7.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-47058?
A fix for CVE-2026-47058 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-47058 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-47058

Explore →

Is Your Infrastructure Affected by CVE-2026-47058?

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

Book a Demo →Browse All CVEs