CVE-2015-0469

HIGHCVSS v2 · 10.010.0
EchelonGraph scoreLOW confidence

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

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 10.0 — NVD rates that HIGH (NVD's v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; no CRITICAL band). Vector AV:N/AC:L/Au:N/C:C/I:C/A:C. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 6.4% exploitation probability in the next 30 days; it does not lift the v2 base. EPSS sets EG Risk's exploitation input. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: NVD CVSS v2.0

Also known asEUVD-2015-0482 (ENISA EUVD) · GHSA-23mh-jxf4-vm3h (GitHub Security Advisories)Source: ENISA EUVD

10.0EG
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: 6.4%CVSS v2: 10.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Unspecified vulnerability in Oracle Java SE 5.0u81, 6u91, 7u76, and 8u40 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to 2D.

CVSS v2.0 (legacy)
10.0HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
10.0HIGHlow confidence
EG Risk
63
EG Risk 63/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)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation6.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
6.4%
EPSS %ILE
93rd
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 (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v2.0 · CVSS v2.0AV:N/AC:L/Au:N/C:C/I:C/A:C
EG Likelihood
6.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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

April 16, 2015

Last Modified

October 14, 2026

References (37)

15 of 37 shown · show the other 22

Patch Availability(13)

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

(4 across 3 ecosystems)
Debian:7(2)
PackageVulnerable rangeFix by version rangeDependents
openjdk-66b27-1.12.5-1 ... 6b35-1.13.7-1~deb6u1 (29 versions)
  • every version up to 6b35-1.13.7-1~deb7u1: fixed in 6b35-1.13.7-1~deb7u1
—
openjdk-77u13-2.3.6-1 ... 7u9-2.3.5~pre1-1 (66 versions)
  • every version up to 7u79-2.5.5-1~deb7u1: fixed in 7u79-2.5.5-1~deb7u1
  • every version up to 7u79-2.5.6-1~deb7u1: fixed in 7u79-2.5.6-1~deb7u1
—
Debian:6.0(1)
PackageVulnerable rangeFix by version rangeDependents
openjdk-66b18-1.8.10-0+squeeze1 ... 6b34-1.13.6-1~deb7u1 (99 versions)
  • every version up to 6b35-1.13.7-1~deb6u1: fixed in 6b35-1.13.7-1~deb6u1
—
Debian:8(1)
PackageVulnerable rangeFix by version rangeDependents
openjdk-77u75-2.5.4-2 ... 7u79-2.5.6-1~deb7u1 (6 versions)
  • every version up to 7u79-2.5.5-1~deb8u1: fixed in 7u79-2.5.5-1~deb8u1
  • every version up to 7u79-2.5.6-1~deb8u1: fixed in 7u79-2.5.6-1~deb8u1
—

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 20× in last 7d / 88× 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 → 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 267 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 167 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(4)

What is CVE-2015-0469?
CVE-2015-0469 is a high-severity vulnerability; its CVE record was published on April 16, 2015. Unspecified vulnerability in Oracle Java SE 5.0u81, 6u91, 7u76, and 8u40 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to 2D.
When was CVE-2015-0469 made public?
CVE-2015-0469 was made public on April 14, 2015: 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 April 16, 2015. EchelonGraph's copy of the record carries a last-modified date of October 14, 2026; the record at its source may have been updated since.
Is CVE-2015-0469 actively exploited?
CVE-2015-0469 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.4% probability of exploitation in the next 30 days (93rd percentile of EPSS-scored CVEs).
How do I remediate CVE-2015-0469?
A fix for CVE-2015-0469 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2015-0469 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-2015-0469

Explore →

Is Your Infrastructure Affected by CVE-2015-0469?

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