WaratekVRT Sign in

Oracle Critical Patch Update April 2025

Released April 2025 · Oracle's advisory ↗ · ← Critical Patch Update, January 2025 · Critical Patch Update, July 2025 →

255 CVEs in this release, one square each

Protected by Waratek, exploitedProtected by Waratek, exploitedProtected by Waratek, exploitedProtected by Waratek, exploitedProtected by Waratek, exploitedProtected by WaratekProtected by WaratekProtected by WaratekProtected by WaratekProtected by WaratekProtected by WaratekProtected by WaratekProtected by WaratekProtected by WaratekProtected by WaratekProtected by WaratekProtected by WaratekProtected by WaratekProtected by WaratekProtected by WaratekProtected by WaratekProtected by WaratekProtected by WaratekMitigation candidate, exploitedMitigation candidateMitigation candidateMitigation candidateMitigation candidateMitigation candidateMitigation candidateMitigation candidateMitigation candidateNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedNo exploit publishedOutside Waratek scopeOutside Waratek scopeOutside Waratek scopeNot applicable, exploitedNot applicable, exploitedNot applicable, exploitedNot applicable, exploitedNot applicable, exploitedNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicable
Share this chart Oracle Critical Patch Update April 2025, one square per CVE: 125 Java CVEs, 23 protected by Waratek, 11 exploited, 130 other CVEs in this release.

Download the image

By status

No exploit published. For 34 of them, Oracle's security advisory is the source of public detail.

Protected by Waratek. Waratek RASP can block exploitation of these on systems that have not applied the patch yet.

Reset
More filters (2)
Columns
Protection: None✕Published from 2020-01-01✕
Overview 102 matches · 0 protected · 1 exploited · 1 CISA KEV · 9 public PoC · 4 EPSS ≥ 0.5
split by peak 30 / quarter
No exploit published: 93Mitigation candidate: 9 Low: 4Medium: 53High: 39Critical: 6 not blocked: 102 No public exploit: 84Forecast only: 2Proof of concept only: 13Working exploit published: 2Exploited: 1
Q1 201 No exploit published1 Medium1 not blocked1 No public exploit1 Q2 201 Mitigation candidate1 High1 not blocked1 Proof of concept only1 Q3 201 Mitigation candidate1 High1 not blocked1 Working exploit published1 Q4 201 No exploit published1 Medium1 not blocked1 Forecast only1 Q1 212 No exploit published2 High1 Medium1 not blocked2 No public exploit2 Q2 212 No exploit published2 High1 Medium1 not blocked2 No public exploit2 Q3 214 No exploit published4 High2 Medium2 not blocked4 Forecast only1 No public exploit3 Q4 213 Mitigation candidate1 No exploit published2 Critical1 Medium2 not blocked3 Proof of concept only1 No public exploit2 Q1 221 No exploit published1 High1 not blocked1 No public exploit1 Q2 221 No exploit published1 High1 not blocked1 No public exploit1 Q3 221 No exploit published1 Low1 not blocked1 No public exploit1 Q4 222 No exploit published2 High2 not blocked2 No public exploit2 Q1 233 No exploit published3 High2 Medium1 not blocked3 Proof of concept only1 No public exploit2 Q2 231 No exploit published1 Medium1 not blocked1 No public exploit1 Q3 234 Mitigation candidate1 No exploit published3 Critical1 Medium2 Low1 not blocked4 Proof of concept only1 No public exploit3 Q4 235 Mitigation candidate2 No exploit published3 High2 Medium3 not blocked5 Exploited1 Working exploit published1 No public exploit3 Q1 249 Mitigation candidate2 No exploit published7 High6 Medium3 not blocked9 Proof of concept only3 No public exploit6 Q2 243 No exploit published3 High3 not blocked3 No public exploit3 Q3 246 No exploit published6 Critical1 High4 Medium1 not blocked6 No public exploit6 Q4 2415 Mitigation candidate1 No exploit published14 Critical2 High1 Medium11 Low1 not blocked15 Proof of concept only3 No public exploit12 Q1 256 No exploit published6 High4 Medium2 not blocked6 Proof of concept only3 No public exploit3 Q2 2530 No exploit published30 Critical1 High7 Medium21 Low1 not blocked30 No public exploit30
Q2 20Q4 20Q2 21Q4 21Q2 22Q4 22Q2 23Q4 23Q2 24Q4 24Q2 25
102 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed. ‹ prev page 2 of 2 next ›
CVE Severity Published▾ Status Exploitation Description
CVE-2020-11996 High 2020-06-26 Mitigation candidate Proof of concept only A specially crafted sequence of HTTP/2 requests sent to Apache Tomcat 10.0.0-M1 to 10.0.0-M5, 9.0.0.M1 to 9.0.35 and 8.5.0 to 8.5.55 could trigger high CPU usage for several seconds. If a sufficient number of such requests were made on concurrent HTTP/2 connections, the server could become unresponsive.
CVE-2020-1935 Medium 2020-02-24 No exploit published No public exploit In Apache Tomcat 9.0.0.M1 to 9.0.30, 8.5.0 to 8.5.50 and 7.0.0 to 7.0.99 the HTTP header parsing code used an approach to end-of-line parsing that allowed some invalid HTTP headers to be parsed as valid. This led to a possibility of HTTP Request Smuggling if Tomcat was located behind a reverse proxy that incorrectly handled the invalid Transfer-Encoding header in a particular manner. Such a reverse proxy is considered unlikely.
‹ prev page 2 of 2 next ›