Java Runtime Environment (JRE) ↗
Auto-added after CISA flagged Java Runtime Environment (JRE) as actively exploited (KEV catalog). Version and lifecycle mapping is pending review, so this is assessed at the product level and is never reported as a confident "healthy".
Summary iPlain-English security verdict for Java Runtime Environment (JRE), generated from its current health score, actively-exploited vulnerabilities, and latest supported version.
Java Runtime Environment (JRE) currently scores 0/100 — critical, with active exploitation. 4 of its known vulnerabilities are being actively exploited in the wild (CISA KEV), including CVE-2012-4681. Upgrade immediately and review your exposure to the actively-exploited CVEs below.
Disclosure trend iNew CVEs published for Java Runtime Environment (JRE) each year (NVD). A higher bar means more disclosures that year — more scrutiny, not necessarily less safe.
4 of its known vulnerabilities are linked to ransomware campaigns (CISA KEV).
Patch priority — what to act on iThe issues to fix first — actively exploited (CISA KEV) first, then by exploitation probability (EPSS), then severity. Each row's "→ fixed in" is the earliest version that patches it; "see advisory" means no fixed version is published.
Most urgent first — actively exploited, then likeliest to be exploited.
CVE-2012-4681 CRITICAL exploited ransomware Improper access control EPSS 99% → see advisory CVE-2012-0507 CRITICAL exploited ransomware CWE-843 EPSS 98% → see advisory CVE-2012-1723 CRITICAL exploited ransomware Improper access control EPSS 94% → see advisory CVE-2013-0431 LOW exploited ransomware CWE-693 EPSS 90% → see advisory CVE-2015-4748 HIGH EPSS 45% → see advisory CVE-2016-9841 CRITICAL EPSS 8% → see advisorySee all 80 known Java Runtime Environment (JRE) CVEs & security history →
Get alerted about Java Runtime Environment (JRE)
Be emailed the moment Java Runtime Environment (JRE) gets a newly exploited vulnerability (CISA KEV) or a release reaches end of life. Free · double opt-in · unsubscribe anytime.
We email only on real events for Java Runtime Environment (JRE) — no marketing, no sharing, and we never know what you run. Track your whole stack →
Frequently asked
Is Java Runtime Environment (JRE) safe and patched?
Java Runtime Environment (JRE) currently scores 0/100 — critical, with active exploitation. 4 of its known vulnerabilities are being actively exploited in the wild (CISA KEV), including CVE-2012-4681. Upgrade immediately and review your exposure to the actively-exploited CVEs below.
What should I do about Java Runtime Environment (JRE) now?
Review the patch-priority list, apply the available fixes (or move to the latest release), and confirm against Oracle's official advisory. Some issues are under active exploitation, so treat this as urgent.
Why is Java Runtime Environment (JRE) listed on IsItPatched?
Java Runtime Environment (JRE) was added automatically because CISA's Known Exploited Vulnerabilities (KEV) catalog flagged it as actively exploited in the wild. IsItPatched tracks its known CVEs, severity (CVSS), exploitation probability (EPSS) and KEV status from public data; its version and lifecycle mapping is verified over time.
Has Java Runtime Environment (JRE) been actively exploited?
Yes. CISA added Java Runtime Environment (JRE) to its Known Exploited Vulnerabilities (KEV) catalog after confirming exploitation in the wild — the triggering vulnerability is CVE-2013-2423. Make sure you are running a patched, supported version of Java Runtime Environment (JRE) and confirm it against Oracle's security advisory.
Similar software we track
More from Oracle tracked on IsItPatched.
lifecycle unknown — needs latest supported version
Informational only, from public data (NVD · CISA KEV · EPSS · endoflife.date), and can lag or miss vendor-specific fixes. Always confirm against Oracle's official advisory before you patch or upgrade — Java Runtime Environment (JRE) official site ↗