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
By status
23Protected by Waratek9Mitigation candidate93No exploit published3Outside Waratek scope127Not applicable
11Exploited, marked by the ring
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.
Overview 101 matches · 0 protected · 1 exploited · 1 CISA KEV · 9 public PoC · 4 EPSS ≥ 0.5
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
9
8.9%
No exploit published
92
91.1%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
101
100.0%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 30 / quarter
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
| 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. |