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 candidate154No exploit published6Outside Waratek scope241Not 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 105 matches · 67 in Waratek scope · 10 protected · 6 exploited · 1 CISA KEV · 9 public PoC · 9 EPSS ≥ 0.5
105matches
67in Waratek scope63.8%
10protected9.5%
6exploited5.7%
1CISA KEV1.0%
9public PoC8.6%
9EPSS ≥ 0.58.6%
Protected by Waratek
10
9.5%
Rule in development
0
0.0%
Mitigation candidate
2
1.9%
No exploit published
55
52.4%
Outside Waratek scope
0
0.0%
Not applicable
38
36.2%
Withdrawn CVE
0
0.0%
blocked by ARMR today
10
9.5%
partly blocked
0
0.0%
not blocked
95
90.5%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 22 / quarter
Q4 201
Protected by Waratek1
Medium1
blocked by ARMR today1
No public exploit1
Q1 211
No exploit published1
High1
not blocked1
No public exploit1
Q2 211
No exploit published1
Medium1
not blocked1
No public exploit1
Q3 210
Q4 211
Protected by Waratek1
Critical1
blocked by ARMR today1
Exploited1
Q1 223
Protected by Waratek3
Critical1
High2
blocked by ARMR today3
Proof of concept only1
Forecast only2
Q2 221
No exploit published1
High1
not blocked1
No public exploit1
Q3 222
No exploit published2
High2
not blocked2
No public exploit2
Q4 224
Protected by Waratek1
No exploit published3
Critical1
High3
blocked by ARMR today1
not blocked3
Proof of concept only3
No public exploit1
Q1 232
Protected by Waratek1
No exploit published1
High2
blocked by ARMR today1
not blocked1
Exploited1
Proof of concept only1
Q2 235
No exploit published5
High2
Medium3
not blocked5
Proof of concept only1
No public exploit4
Q3 233
No exploit published3
Critical1
High2
not blocked3
No public exploit3
Q4 234
No exploit published3
Not applicable1
Critical2
Medium2
not blocked4
Exploited1
Proof of concept only1
No public exploit2
Q1 245
No exploit published4
Not applicable1
Critical1
High1
Medium3
not blocked5
Proof of concept only1
No public exploit4
Q2 248
No exploit published4
Not applicable4
Critical2
High4
Medium2
not blocked8
Proof of concept only1
No public exploit7
Q3 245
No exploit published4
Not applicable1
Critical1
High4
not blocked5
Exploited1
No public exploit4
Q4 246
Protected by Waratek1
No exploit published5
Critical2
Medium4
blocked by ARMR today1
not blocked5
Proof of concept only2
No public exploit4
Q1 259
Mitigation candidate1
No exploit published3
Not applicable5
High6
Medium3
not blocked9
Exploited1
Proof of concept only5
No public exploit3
Q2 2522
Protected by Waratek2
Mitigation candidate1
No exploit published11
Not applicable8
Critical1
High13
Medium7
Low1
blocked by ARMR today2
not blocked20
Exploited1
Proof of concept only4
No public exploit17
Q3 2522
No exploit published4
Not applicable18
High9
Medium10
Low3
not blocked22
Working exploit published2
Proof of concept only3
No public exploit17
Q1 21Q3 21Q1 22Q3 22Q1 23Q3 23Q1 24Q3 24Q1 25Q3 25
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2022-23302 | High | 2022-01-18 | Protected by Waratek | Forecast only | JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions. |
| CVE-2021-45046 | Critical | 2021-12-14 | Protected by Waratek | Exploited | It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allows attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in an information leak and remote code execution in some environments and local code execution in all environments. Log4j 2.16.0 (Java 8) and 2.12.2 (Java 7) fix this issue by removing support for message lookup patterns and disabling JNDI functionality by default. |
| CVE-2021-28168 | Medium | 2021-04-22 | No exploit published | No public exploit | Eclipse Jersey 2.28 to 2.33 and Eclipse Jersey 3.0.0 to 3.0.1 contains a local information disclosure vulnerability. This is due to the use of the File.createTempFile which creates a file inside of the system temporary directory with the permissions: -rw-r--r--. Thus the contents of this file are viewable by all other users locally on the system. As such, if the contents written is security sensitive, it can be disclosed to other local users. |
| CVE-2021-0341 | High | 2021-02-10 | No exploit published | No public exploit | In verifyHostName of OkHostnameVerifier.java, there is a possible way to accept a certificate for the wrong domain due to improperly used crypto. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-8.1 Android-9 Android-10 Android-11Android ID: A-171980069 |
| CVE-2020-17521 | Medium | 2020-12-07 | Protected by Waratek | No public exploit | Apache Groovy provides extension methods to aid with creating temporary directories. Prior to this fix, Groovy's implementation of those extension methods was using a now superseded Java JDK method call that is potentially not secure on some operating systems in some contexts. Users not using the extension methods mentioned in the advisory are not affected, but may wish to read the advisory for further details. Versions Affected: 2.0 to 2.4.20, 2.5.0 to 2.5.13, 3.0.0 to 3.0.6, and 4.0.0-alpha-1. Fixed in versions 2.4.21, 2.5.14, 3.0.7, 4.0.0-alpha-2. |