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 · 16 protected · 5 exploited · 2 CISA KEV · 11 public PoC · 3 EPSS ≥ 0.5
Protected by Waratek
16
15.8%
Rule in development
0
0.0%
Mitigation candidate
6
5.9%
No exploit published
79
78.2%
blocked by ARMR today
16
15.8%
partly blocked
0
0.0%
not blocked
85
84.2%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 31 / quarter
Q3 221
No exploit published1
Low1
not blocked1
No public exploit1
Q4 224
Protected by Waratek2
No exploit published2
Critical1
High3
blocked by ARMR today2
not blocked2
Proof of concept only1
No public exploit3
Q1 235
Protected by Waratek2
No exploit published3
High4
Medium1
blocked by ARMR today2
not blocked3
Exploited1
Proof of concept only1
No public exploit3
Q2 231
No exploit published1
Medium1
not blocked1
No public exploit1
Q3 236
Protected by Waratek2
Mitigation candidate1
No exploit published3
Critical1
High1
Medium3
Low1
blocked by ARMR today2
not blocked4
Proof of concept only1
No public exploit5
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 248
Protected by Waratek2
No exploit published6
Critical1
High6
Medium1
blocked by ARMR today2
not blocked6
Exploited1
Proof of concept only1
No public exploit6
Q4 2421
Protected by Waratek6
Mitigation candidate1
No exploit published14
Critical5
High3
Medium12
Low1
blocked by ARMR today6
not blocked15
Exploited1
Working exploit published1
Proof of concept only3
No public exploit16
Q1 257
Protected by Waratek1
No exploit published6
Critical1
High4
Medium2
blocked by ARMR today1
not blocked6
Exploited1
Proof of concept only3
No public exploit3
Q2 2531
Protected by Waratek1
No exploit published30
Critical1
High8
Medium21
Low1
blocked by ARMR today1
not blocked30
No public exploit31
Q3 22Q4 22Q1 23Q2 23Q3 23Q4 23Q1 24Q2 24Q3 24Q4 24Q1 25Q2 25
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2021-43980 | Low | 2022-09-28 | No exploit published | No public exploit | The simplified implementation of blocking reads and writes introduced in Tomcat 10 and back-ported to Tomcat 9.0.47 onwards exposed a long standing (but extremely hard to trigger) concurrency bug in Apache Tomcat 10.1.0 to 10.1.0-M12, 10.0.0-M1 to 10.0.18, 9.0.0-M1 to 9.0.60 and 8.5.0 to 8.5.77 that could cause client connections to share an Http11Processor instance resulting in responses, or part responses, to be received by the wrong client. |