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
22Protected by Waratek8Mitigation candidate88No exploit published16Outside Waratek scope121Not applicable
11Exploited, marked by the ring
No exploit published. For 33 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 202 matches · 93 in Waratek scope · 12 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
202matches
93in Waratek scope46.0%
12protected5.9%
0exploited0.0%
0CISA KEV0.0%
0public PoC0.0%
0EPSS ≥ 0.50.0%
Protected by Waratek
12
5.9%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
81
40.1%
Outside Waratek scope
11
5.4%
Not applicable
98
48.5%
Withdrawn CVE
0
0.0%
blocked by ARMR today
12
5.9%
partly blocked
0
0.0%
not blocked
190
94.1%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
202
100.0%
split by
peak 74 / quarter
Q1 201
No exploit published1
Medium1
not blocked1
No public exploit1
Q2 200
Q3 200
Q4 201
Protected by Waratek1
High1
blocked by ARMR today1
No public exploit1
Q1 214
Protected by Waratek2
No exploit published2
High3
Medium1
blocked by ARMR today2
not blocked2
No public exploit4
Q2 212
No exploit published1
Outside Waratek scope1
High1
Medium1
not blocked2
No public exploit2
Q3 213
No exploit published3
High2
Medium1
not blocked3
No public exploit3
Q4 212
No exploit published1
Outside Waratek scope1
Critical1
Medium1
not blocked2
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 223
Protected by Waratek1
No exploit published2
High3
blocked by ARMR today1
not blocked2
No public exploit3
Q1 233
Protected by Waratek1
No exploit published2
High2
Medium1
blocked by ARMR today1
not blocked2
No public exploit3
Q2 231
No exploit published1
Medium1
not blocked1
No public exploit1
Q3 236
Protected by Waratek2
No exploit published3
Not applicable1
Critical1
High1
Medium3
Low1
blocked by ARMR today2
not blocked4
No public exploit6
Q4 235
No exploit published3
Not applicable2
High2
Medium2
Low1
not blocked5
No public exploit5
Q1 2411
No exploit published6
Not applicable5
Critical2
High4
Medium5
not blocked11
No public exploit11
Q2 2410
No exploit published3
Outside Waratek scope2
Not applicable5
Critical1
High4
Medium5
not blocked10
No public exploit10
Q3 2418
No exploit published6
Not applicable12
Critical3
High5
Medium10
not blocked18
No public exploit18
Q4 2436
Protected by Waratek4
No exploit published11
Outside Waratek scope2
Not applicable19
Critical5
High9
Medium21
Low1
blocked by ARMR today4
not blocked32
No public exploit36
Q1 2519
No exploit published3
Outside Waratek scope3
Not applicable13
Critical1
High10
Medium8
not blocked19
No public exploit19
Q2 2574
Protected by Waratek1
No exploit published30
Outside Waratek scope2
Not applicable41
Critical1
High13
Medium56
Low4
blocked by ARMR today1
not blocked73
No public exploit74
Q2 20Q4 20Q2 21Q4 21Q2 22Q4 22Q2 23Q4 23Q2 24Q4 24Q2 25
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2020-25649 | High | 2020-12-03 | Protected by Waratek | No public exploit | A flaw was found in FasterXML Jackson Databind, where it did not have entity expansion secured properly. This flaw allows vulnerability to XML external entity (XXE) attacks. The highest threat from this vulnerability is data integrity. |
| 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. |