CVE-2017-10111

CRITICALNVD 9.69.6
EchelonGraph scoreMEDIUM confidence

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

Score 9.6 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-13. NVD baseline CVSS 9.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2017-1758 (ENISA EUVD) · GHSA-mjf8-xvj5-3g9h (GitHub Security Advisories)Source: ENISA EUVD

9.6EG
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: 2.1%CVSS: 9.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Vulnerability in the Java SE, Java SE Embedded component of Oracle Java SE (subcomponent: Libraries). The supported version that is affected is Java SE: 8u131; Java SE Embedded: 8u131. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE, Java SE Embedded. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Java SE, Java SE Embedded, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of Java SE, Java SE Embedded. Note: This vulnerability 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. This vulnerability does not apply to Java deployments, typically in servers, that load and run only trusted code (e.g., code installed by an administrator). CVSS 3.0 Base Score 9.6 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H).

CVSS v3
9.6
EG Score
9.6CRITICALmedium confidence
EG Risk
44
EG Risk 44/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)
Severity96% × 45%
Impact severity (EG Severity): CVSS 9.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation2.1% × 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
2.1%
EPSS %ILE
81st
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.6): severity, escalated by confirmed exploitation. This CVE's 9.6 is its impact severity (EG Severity), not escalated.

EG Severity
9.6 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
2.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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, 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; 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.

The score's inputs: 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

August 8, 2017

Last Modified

June 17, 2026

Advisory Details (7)

Auto-updated Oct 7, 2026
Patch available. Sources: redhat.
Web page

[SECURITY] [DSA 3919-1] openjdk-8 security update

http://www.debian.org/security/2017/dsa-3919
Web page

NetApp Product Security

https://security.netapp.com/advisory/ntap-20170720-0001/
Web page

Oracle JDK/JRE, IcedTea: Multiple vulnerabilities (GLSA 201709-22) — Gentoo security

https://security.gentoo.org/glsa/201709-22
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 6 and Oracle Java for Red Hat Enterprise Linux 7.

https://access.redhat.com/errata/RHSA-2017:1790
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 6 and Red Hat Enterprise Linux 7.

https://access.redhat.com/errata/RHSA-2017:1789
Web page

CVE-2017-10111 - PSIRT.COM

http://www.securityfocus.com/bid/99707
Web page
http://www.securitytracker.com/id/1038931

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuopenjdk-8-source (8u131-b11-2ubuntu1.16.04.2) @ xenial2026-11-01ubuntu
redhatjava-1.8.0-oracle-1:1.8.0.141-1jpp.1.el7_32017-07-20redhat
redhatjava-1.8.0-openjdk-1:1.8.0.141-1.b16.el7_32017-07-20redhat

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:9(1)
PackageVulnerable rangeFix by version rangeDependents
openjdk-88u131-b11-2
  • every version up to 8u141-b15-1~deb9u1: fixed in 8u141-b15-1~deb9u1
—

All Vendor Advisories

(3)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 26× 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 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 98 of 238 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 140 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor)

Frequently asked(5)

What is CVE-2017-10111?
CVE-2017-10111 is a critical-severity vulnerability; its CVE record was published on August 8, 2017. Vulnerability in the Java SE, Java SE Embedded component of Oracle Java SE (subcomponent: Libraries). The supported version that is affected is Java SE: 8u131; Java SE Embedded: 8u131. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to…
When was CVE-2017-10111 made public?
CVE-2017-10111 was made public on July 18, 2017: that is the date its CVE record's CNA, Oracle, gives for when the vulnerability was made public. The CVE record itself was published on August 8, 2017. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2017-10111 actively exploited?
CVE-2017-10111 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.1% probability of exploitation in the next 30 days (81st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-10111?
CVE-2017-10111 has a CVSS v3 base score of 9.6 (NVD).
How do I remediate CVE-2017-10111?
A fix for CVE-2017-10111 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-10111

Explore →

Is Your Infrastructure Affected by CVE-2017-10111?

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

Book a Demo →Browse All CVEs