CVE-2016-0483

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 15% exploitation probability in the next 30 days; it does not lift the v2 base. EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated) sets EG Risk's exploitation input, not EPSS. Confidence: LOW.

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

Also known asEUVD-2016-0518 (ENISA EUVD) · GHSA-7xjq-3wg8-c44c (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: 15%CVSS v2: 10.0Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Unspecified vulnerability in Oracle Java SE 6u105, 7u91, and 8u66; Java SE Embedded 8u65; and JRockit R28.3.8 allows remote attackers to affect confidentiality, integrity, and availability via vectors related to AWT. NOTE: the previous information is from the January 2016 CPU. Oracle has not commented on third-party claims that this is a heap-based buffer overflow in the readImage function, which allows remote attackers to execute arbitrary code via crafted image data.

CVSS v2.0 (legacy)
10.0HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
10.0HIGHlow confidence
EG Risk
76
EG Risk 76/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.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
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
15%
EPSS %ILE
96th
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
15% 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

January 21, 2016

Last Modified

October 15, 2026

References (27)

15 of 27 shown · show the other 12

Patch Availability(15)

These rows come from Ubuntu and Red Hat. 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 ... 6b38-1.13.10-1~deb6u1 (37 versions)
  • every version up to 6b38-1.13.10-1~deb7u1: fixed in 6b38-1.13.10-1~deb7u1
—
openjdk-77u13-2.3.6-1 ... 7u91-2.6.3-3 (84 versions)
  • every version up to 7u95-2.6.4-1~deb7u1: fixed in 7u95-2.6.4-1~deb7u1
—
Debian:6.0(1)
PackageVulnerable rangeFix by version rangeDependents
openjdk-66b18-1.8.10-0+squeeze1 ... 6b37-1.13.9-1~deb6u1 (107 versions)
  • every version up to 6b38-1.13.10-1~deb6u1: fixed in 6b38-1.13.10-1~deb6u1
—
Debian:8(1)
PackageVulnerable rangeFix by version rangeDependents
openjdk-77u75-2.5.4-2 ... 7u95-2.6.4-1~deb7u1 (25 versions)
  • every version up to 7u95-2.6.4-1~deb8u1: fixed in 7u95-2.6.4-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 299 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 199 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(4)

What is CVE-2016-0483?
CVE-2016-0483 is a high-severity vulnerability; its CVE record was published on January 21, 2016. Unspecified vulnerability in Oracle Java SE 6u105, 7u91, and 8u66; Java SE Embedded 8u65; and JRockit R28.3.8 allows remote attackers to affect confidentiality, integrity, and availability via vectors related to AWT. NOTE: the previous information is from the January 2016 CPU. Oracle has not…
When was CVE-2016-0483 made public?
CVE-2016-0483 was made public on January 19, 2016: 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 January 21, 2016. EchelonGraph's copy of the record carries a last-modified date of October 15, 2026; the record at its source may have been updated since.
Is CVE-2016-0483 actively exploited?
CVE-2016-0483 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 15% probability of exploitation in the next 30 days (96th percentile of EPSS-scored CVEs).
How do I remediate CVE-2016-0483?
A fix for CVE-2016-0483 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2016-0483 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-2016-0483

Explore →

Is Your Infrastructure Affected by CVE-2016-0483?

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