Oracle Java (JDK) vulnerabilities: known CVEs & security history
Oracle · Web / Runtime · 79 tracked CVEs · 2 actively exploited · updated October 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Oracle Java (JDK) release lines — 79 in total, with 2 actively exploited in the wild. A CVE here doesn't mean your version is affected — check Oracle Java (JDK)'s current status and the safe version to run.
Known Oracle Java (JDK) CVEs
Actively-exploited and most-severe first. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2012-4681⚡ exploited | critical | 9.8 | 99% | 2012 |
| CVE-2012-1723⚡ exploited | critical | 9.8 | 94% | 2012 |
| CVE-2016-9841 | critical | 9.8 | 8% | 2017 |
| CVE-2016-0494 | high | 10 | 7% | 2016 |
| CVE-2016-0483 | high | 10 | 15% | 2016 |
| CVE-2015-4883 | high | 10 | 6% | 2015 |
| CVE-2015-4881 | high | 10 | 6% | 2015 |
| CVE-2015-4860 | high | 10 | 6% | 2015 |
| CVE-2015-4844 | high | 10 | 8% | 2015 |
| CVE-2015-4843 | high | 10 | 10% | 2015 |
| CVE-2015-4835 | high | 10 | 7% | 2015 |
| CVE-2015-4805 | high | 10 | 6% | 2015 |
| CVE-2015-4760 | high | 10 | 7% | 2015 |
| CVE-2015-4732 | high | 10 | 7% | 2015 |
| CVE-2015-4731 | high | 10 | 6% | 2015 |
| CVE-2015-2638 | high | 10 | 6% | 2015 |
| CVE-2015-2628 | high | 10 | 6% | 2015 |
| CVE-2015-0469 | high | 10 | 6% | 2015 |
| CVE-2016-9842 | high | 8.8 | 5% | 2017 |
| CVE-2016-9840 | high | 8.8 | 5% | 2017 |
| CVE-2026-62574 | high | 7.8 | 0% | 2026 |
| CVE-2018-2811 | high | 7.7 | 0% | 2018 |
| CVE-2015-4748 | high | 7.6 | 45% | 2015 |
| CVE-2026-47063 | high | 7.5 | 0% | 2026 |
| CVE-2026-47057 | high | 7.5 | 0% | 2026 |
| CVE-2026-34282 | high | 7.5 | 1% | 2026 |
| CVE-2026-22016 | high | 7.5 | 1% | 2026 |
| CVE-2026-21945 | high | 7.5 | 1% | 2026 |
| CVE-2025-53066 | high | 7.5 | 1% | 2025 |
| CVE-2015-8126 | high | 7.5 | 10% | 2015 |
| CVE-2026-47058 | high | 7.4 | 0% | 2026 |
| CVE-2026-21932 | high | 7.4 | 0% | 2026 |
| CVE-2015-2664 | medium | 6.9 | 0% | 2015 |
| CVE-2026-60526 | medium | 6.7 | 0% | 2026 |
| CVE-2026-60147 | medium | 6.5 | 0% | 2026 |
| CVE-2019-16168 | medium | 6.5 | 4% | 2019 |
| CVE-2018-11212 | medium | 6.5 | 5% | 2018 |
| CVE-2015-4806 | medium | 6.4 | 4% | 2015 |
| CVE-2019-10219 | medium | 6.1 | 2% | 2019 |
| CVE-2026-22003 | medium | 6 | 0% | 2026 |
| CVE-2026-46968 | medium | 5.9 | 0% | 2026 |
| CVE-2025-53057 | medium | 5.9 | 1% | 2025 |
| CVE-2016-0475 | medium | 5.8 | 4% | 2016 |
| CVE-2026-47027 | medium | 5.3 | 0% | 2026 |
| CVE-2026-47021 | medium | 5.3 | 0% | 2026 |
| CVE-2026-47013 | medium | 5.3 | 0% | 2026 |
| CVE-2026-46917 | medium | 5.3 | 0% | 2026 |
| CVE-2026-22021 | medium | 5.3 | 0% | 2026 |
| CVE-2026-22013 | medium | 5.3 | 0% | 2026 |
| CVE-2016-0466 | medium | 5 | 5% | 2016 |
| CVE-2016-0402 | medium | 5 | 5% | 2016 |
| CVE-2015-4911 | medium | 5 | 4% | 2015 |
| CVE-2015-4903 | medium | 5 | 4% | 2015 |
| CVE-2015-4893 | medium | 5 | 5% | 2015 |
| CVE-2015-4882 | medium | 5 | 4% | 2015 |
| CVE-2015-4872 | medium | 5 | 4% | 2015 |
| CVE-2015-4842 | medium | 5 | 5% | 2015 |
| CVE-2015-4840 | medium | 5 | 4% | 2015 |
| CVE-2015-4803 | medium | 5 | 5% | 2015 |
| CVE-2015-4734 | medium | 5 | 5% | 2015 |
| CVE-2015-2637 | medium | 5 | 3% | 2015 |
| CVE-2015-2621 | medium | 5 | 4% | 2015 |
| CVE-2015-2601 | medium | 5 | 4% | 2015 |
| CVE-2014-0459 | medium | 4.3 | 4% | 2014 |
| CVE-2016-0448 | medium | 4 | 4% | 2016 |
| CVE-2026-47059 | low | 3.7 | 0% | 2026 |
| CVE-2026-47010 | low | 3.7 | 0% | 2026 |
| CVE-2026-22018 | low | 3.7 | 0% | 2026 |
| CVE-2026-22008 | low | 3.7 | 0% | 2026 |
| CVE-2025-61748 | low | 3.7 | 0% | 2025 |
| CVE-2026-60166 | low | 3.1 | 0% | 2026 |
| CVE-2026-60164 | low | 3.1 | 0% | 2026 |
| CVE-2026-47035 | low | 3.1 | 0% | 2026 |
| CVE-2026-47034 | low | 3.1 | 0% | 2026 |
| CVE-2026-47030 | low | 3.1 | 0% | 2026 |
| CVE-2026-34268 | low | 2.9 | 0% | 2026 |
| CVE-2026-22007 | low | 2.9 | 0% | 2026 |
| CVE-2015-2627 | low | 2.6 | 3% | 2015 |
| CVE-2015-2625 | low | 2.6 | 4% | 2015 |
Is my Oracle Java (JDK) version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your Oracle Java (JDK) version → · Monitor Oracle Java (JDK) for new CVEs →
Oracle Java (JDK) vulnerabilities — frequently asked
How many known vulnerabilities does Oracle Java (JDK) have?
IsItPatched tracks 79 CVEs for Oracle Java (JDK), 2 of which are actively exploited (CISA KEV). 3 are critical-severity and 29 high-severity. These span every release line — what matters is whether the version you run is affected.
Does Oracle Java (JDK) have any actively-exploited vulnerabilities?
Yes — 2 Oracle Java (JDK) CVEs are in CISA's Known Exploited Vulnerabilities catalog, meaning they are confirmed exploited in the wild (2 linked to ransomware). Patch these as a priority.
What is the most severe Oracle Java (JDK) vulnerability?
Among tracked issues, CVE-2012-4681 (CRITICAL, CVSS 9.8), which is actively exploited, ranks highest — a Improper access control weakness.
Is Oracle Java (JDK) safe to use?
It depends on the version. The latest supported Oracle Java (JDK) release clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Oracle Java (JDK) security status · Oracle Java (JDK) end-of-life · actively-exploited CVEs. Always verify against Oracle's advisories — see our disclaimer.