Oracle Critical Patch Update April 2026
Released April 2026 · Oracle's advisory ↗ · ← Critical Patch Update, January 2026 · Security Patch Update, May 2026 →
421 CVEs in this release, one square each
By status
16Protected by Waratek4Mitigation candidate152No exploit published10Outside Waratek scope239Not applicable
8Exploited, marked by the ring
No exploit published. For 51 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 104 matches · 0 protected · 1 exploited · 0 CISA KEV · 1 public PoC · 0 EPSS ≥ 0.5
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
2
1.9%
No exploit published
102
98.1%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
104
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
1
1.0%
Working exploit published
0
0.0%
Proof of concept only
9
8.7%
Forecast only
0
0.0%
No public exploit
94
90.4%
split by
peak 55 / month
Jul 254
No exploit published4
Medium4
not blocked4
Proof of concept only1
No public exploit3
Aug 254
No exploit published4
Critical1
High1
Medium2
not blocked4
No public exploit4
Sep 257
Mitigation candidate1
No exploit published6
High2
Medium4
Low1
not blocked7
Exploited1
Proof of concept only1
No public exploit5
Oct 254
No exploit published4
High1
Medium3
not blocked4
Proof of concept only1
No public exploit3
Nov 252
No exploit published2
Critical1
High1
not blocked2
No public exploit2
Dec 2512
No exploit published12
High5
Medium6
Low1
not blocked12
Proof of concept only2
No public exploit10
Jan 265
No exploit published5
Critical2
High3
not blocked5
Proof of concept only1
No public exploit4
Feb 268
No exploit published8
Critical1
High3
Medium3
Low1
not blocked8
No public exploit8
Mar 263
No exploit published3
High2
Medium1
not blocked3
Proof of concept only2
No public exploit1
Apr 2655
Mitigation candidate1
No exploit published54
Critical5
High13
Medium33
Low4
not blocked55
Proof of concept only1
No public exploit54
Jul 25Aug 25Sep 25Oct 25Nov 25Dec 25Jan 26Feb 26Mar 26Apr 26
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2025-7962 | Medium | 2025-07-21 | No exploit published | No public exploit | In Jakarta Mail versions prior to 2.0.2 it is possible to perform an SMTP Injection by utilizing the \r and \n UTF-8 characters to separate different messages. |
| CVE-2025-48795 | Medium | 2025-07-15 | No exploit published | No public exploit | Apache CXF stores large stream based messages as temporary files on the local filesystem. A bug was introduced which means that the entire temporary file is read into memory and then logged. An attacker might be able to exploit this to cause a denial of service attack by causing an out of memory exception. In addition, it is possible to configure CXF to encrypt temporary files to prevent sensitive credentials from being cached unencrypted on the local filesystem, however this bug means that the cached files are written out to logs unencrypted. Users are recommended to upgrade to versions 3.5.11, 3.6.6, 4.0.7 or 4.1.1, which fixes this issue. |
| CVE-2025-53864 | Medium | 2025-07-11 | No exploit published | Proof of concept only | Connect2id Nimbus JOSE + JWT 10.0.x before 10.0.2 and 9.37.x before 9.37.4 allows a remote attacker to cause a denial of service via a deeply nested JSON object supplied in a JWT claim set, because of uncontrolled recursion. NOTE: this is independent of the Gson 2.11.0 issue because the Connect2id product could have checked the JSON object nesting depth, regardless of what limits (if any) were imposed by Gson. |
| CVE-2025-48924 | Medium | 2025-07-11 | No exploit published | No public exploit | Uncontrolled Recursion vulnerability in Apache Commons Lang. This issue affects Apache Commons Lang: Starting with commons-lang:commons-lang 2.0 to 2.6, and, from org.apache.commons:commons-lang3 3.0 before 3.18.0. The methods ClassUtils.getClass(...) can throw StackOverflowError on very long inputs. Because an Error is usually not handled by applications and libraries, a StackOverflowError could cause an application to stop. Users are recommended to upgrade to version 3.18.0, which fixes the issue. |