CVE-2019-2698

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2022-05-24. NVD baseline CVSS 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
8.1EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • Public exploit code is available (Exploit-DB (verified), epss top5pct, public exploit)
CISA-KEV: Not listedEPSS PROB: 12%CVSS: 8.1Exploit: Exploit-DB (verified) · epss top5pct · public exploitExposed: 0

A fix is available — apply it.

Vulnerability in the Java SE component of Oracle Java SE (subcomponent: 2D). Supported versions that are affected are Java SE: 7u211 and 8u202. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE. Successful attacks of this vulnerability can result in takeover of Java SE. Note: This vulnerability applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets (in Java SE 8), 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 8.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H).

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
62(Track)
EG Risk 62/100SSVC: Track

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
Severity81% × 45%
Exploitation65% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
12%
EPSS %ILE
96%
KEV
Not listed

Published

April 23, 2019

Last Modified

November 21, 2024

References (36)

Patch Availability(11)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuopenjdk-8-source (8u212-b03-0ubuntu1.19.04.2) @ disco2026-05-27ubuntu
redhatjava-1.8.0-ibm-1:1.8.0.5.35-1jpp.1.el6_102019-06-04redhat
redhatjava-1.8.0-ibm-1:1.8.0.5.35-3.el8_02019-05-16redhat
redhatjava-1.7.1-ibm-1:1.7.1.4.45-1jpp.1.el6_102019-05-13redhat
redhatjava-1.7.1-ibm-1:1.7.1.4.45-1jpp.1.el72019-05-13redhat
redhatjava-1.8.0-ibm-1:1.8.0.5.35-1jpp.1.el72019-05-13redhat
redhatjava-1.8.0-openjdk-1:1.8.0.212.b04-1.el8_02019-05-13redhat
redhatjava-1.7.0-openjdk-1:1.7.0.221-2.6.18.0.el6_102019-04-22redhat
redhatjava-1.7.0-openjdk-1:1.7.0.221-2.6.18.0.el7_62019-04-22redhat
redhatjava-1.8.0-openjdk-1:1.8.0.212.b04-0.el6_102019-04-17redhat
redhatjava-1.8.0-openjdk-1:1.8.0.212.b04-0.el7_62019-04-17redhat

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

(3 across 3 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
openjdk-11—11.0.3+7-1—
Debian:8(1)
PackageVulnerable rangeFixed inDependents
openjdk-77u101-2.6.6-1 ... 7u95-2.6.4-3 (68 versions)7u221-2.6.18-1~deb8u1—
Debian:9(1)
PackageVulnerable rangeFixed inDependents
openjdk-88u131-b11-2 ... 8u212-b03-1 (28 versions)8u212-b03-2~deb9u1—

All Vendor Advisories

(12)

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 3× in last 7d / 22× 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 108 total refreshes for this CVE.

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

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-46723✓ verified
    First seen Apr 17, 2019

    Oracle Java Runtime Environment - Heap Corruption During TTF font Rendering in GlyphIterator::setCurrGlyphID

    Open source ↗

Frequently asked(5)

What is CVE-2019-2698?
CVE-2019-2698 is a high vulnerability published on April 23, 2019. Vulnerability in the Java SE component of Oracle Java SE (subcomponent: 2D). Supported versions that are affected are Java SE: 7u211 and 8u202. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE. Successful attacks of…
When was CVE-2019-2698 disclosed?
CVE-2019-2698 was first published in the National Vulnerability Database on April 23, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-2698 actively exploited?
CVE-2019-2698 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 12% probability of exploitation in the next 30 days, which ranks it in the top 4.2% of all scored CVEs.
What is the CVSS score of CVE-2019-2698?
CVE-2019-2698 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2019-2698?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-2698, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-2698

Explore →

Is Your Infrastructure Affected by CVE-2019-2698?

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

Start Free Scan →Browse All CVEs