CVE-2015-4731

HIGHCVSS v2 · 10.010.0—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 10.0 — v2 rates that HIGH (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has 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 5.8% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: epss, nvd_v2
10.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 5.8%CVSS v2: 10.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Unspecified vulnerability in Oracle Java SE 6u95, 7u80, and 8u45; Java SE Embedded 7u75; and Java SE Embedded 8u33 allows remote attackers to affect confidentiality, integrity, and availability via vectors related to JMX.

CVSS v2.0 (legacy)
10.0HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
10.0HIGHlow confidence
EG Risk
52
EG Risk 52/100CISA SSVC

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
Severity100% × 45%
Exploitation6% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).
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
5.8%
EPSS %ILE
92nd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Track* or 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 (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 16, 2015

Last Modified

May 6, 2026

References (50)

Vendor Advisories for CVE-2015-4731(12)

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

Patch Availability(14)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuopenjdk-7-jre (7u79-2.5.6-0ubuntu1.15.04.1) @ vivid2026-05-23ubuntu
ubuntuopenjdk-6-jre-lib (6b36-1.13.8-0ubuntu1~12.04) @ precise2026-05-23ubuntu
ubuntuopenjdk-7-jre-zero (7u79-2.5.6-0ubuntu1.15.04.1) @ vivid2026-05-23ubuntu
redhatjava-1.6.0-ibm-1:1.6.0.16.7-1jpp.1.el6_72015-08-12redhat
redhatjava-1.5.0-ibm-1:1.5.0.16.13-1jpp.3.el6_72015-08-04redhat
redhatjava-1.6.0-openjdk-1:1.6.0.36-1.13.8.1.el7_12015-07-30redhat
redhatjava-1.7.0-ibm-1:1.7.0.9.10-1jpp.2.el52015-07-23redhat
redhatjava-1.7.1-ibm-1:1.7.1.3.10-1jpp.1.ael7b_12015-07-22redhat
redhatjava-1.6.0-sun-1:1.6.0.101-1jpp.1.el7_12015-07-17redhat
redhatjava-1.8.0-oracle-1:1.8.0.51-1jpp.2.el7_12015-07-17redhat
redhatjava-1.7.0-oracle-1:1.7.0.85-1jpp.2.el7_12015-07-17redhat
redhatjava-1.8.0-openjdk-1:1.8.0.51-1.b16.ael7b_12015-07-15redhat
redhatjava-1.7.0-openjdk-1:1.7.0.85-2.6.1.2.ael7b_12015-07-15redhat
redhatjava-1.7.0-openjdk-1:1.7.0.85-2.6.1.3.el5_112015-07-15redhat

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 ... 6b36-1.13.8-1~deb6u1 (32 versions)
  • every version up to 6b36-1.13.8-1~deb7u1: fixed in 6b36-1.13.8-1~deb7u1
—
openjdk-77u13-2.3.6-1 ... 7u9-2.3.5~pre1-1 (66 versions)
  • 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 ... 6b35-1.13.7-1~deb7u1 (102 versions)
  • every version up to 6b36-1.13.8-1~deb6u1: fixed in 6b36-1.13.8-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.6-1~deb8u1: fixed in 7u79-2.5.6-1~deb8u1
—

Additional Vendor Advisories

(3)

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 7× in last 7d / 21× 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 150 total refreshes for this CVE.

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

Related CVEs(same product + same vendor)

Frequently asked(4)

What is CVE-2015-4731?
CVE-2015-4731 is a high vulnerability published on July 16, 2015. Unspecified vulnerability in Oracle Java SE 6u95, 7u80, and 8u45; Java SE Embedded 7u75; and Java SE Embedded 8u33 allows remote attackers to affect confidentiality, integrity, and availability via vectors related to JMX.
When was CVE-2015-4731 disclosed?
CVE-2015-4731 was first published on July 16, 2015, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2015-4731 actively exploited?
CVE-2015-4731 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5.8% probability of exploitation in the next 30 days (92nd percentile of EPSS-scored CVEs).
How do I remediate CVE-2015-4731?
A fix for CVE-2015-4731 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2015-4731 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-4731

Explore →

Is Your Infrastructure Affected by CVE-2015-4731?

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

Book a Demo →Browse All CVEs