Threats / Oracle / CVE-2015-2590
CVE-2015-2590
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Oracle Java SE vulnerability
An unspecified vulnerability in Oracle Java SE allows remote code execution. The vulnerability has been exploited in the wild with a moderate EPSS score of 0.666.
Verdict
Today item — known-exploited.
This vulnerability poses a significant risk due to active exploitation and the widespread deployment of Java SE across enterprise and consumer environments. Remote code execution capability enables full system compromise without authentication.
CISA KEV Yes · 2022-03-034EPSS 0.25469 (verify live)5CVSS 9.8 (CISA)3CISA SSVC Exploitation: active · Automatable: yes · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
9 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-03-03).
Probability (EPSS)
EPSS 0.25469 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: Oracle, Java SE. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 2422 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious Java application or applet that triggers the unspecified vulnerability in the target's Java Runtime Environment.
Business
Attackers gain arbitrary code execution on systems running vulnerable Java SE versions, enabling data theft, malware installation, and lateral movement.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I deliver the exploit through web browsers, email attachments, or compromised websites that execute Java code in the victim's runtime context.
Business
Organizations face rapid infection across user endpoints without requiring user interaction beyond normal browsing or application usage.
3
Lateral reach — past segmentation narrative 3
Attacker
I establish persistent access and escalate privileges to move through the network infrastructure.
Business
Compromised systems become entry points for advanced persistent threats, leading to data exfiltration and operational disruption.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05