Oracle Critical Security Patch Update November 2026
Released November 2026 · Oracle's advisory ↗ · ← Critical Patch Update, October 2026
942 CVEs in this release, one square each
By status
9Protected by Waratek4Mitigation candidate625No exploit published15Outside Waratek scope289Not applicable
6Exploited, marked by the ring
No exploit published. For 554 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 · 63 in Waratek scope · 3 protected · 3 exploited · 2 CISA KEV · 3 public PoC · 3 EPSS ≥ 0.5
101matches
63in Waratek scope62.4%
3protected3.0%
3exploited3.0%
2CISA KEV2.0%
3public PoC3.0%
3EPSS ≥ 0.53.0%
Protected by Waratek
3
3.0%
Rule in development
0
0.0%
Mitigation candidate
1
1.0%
No exploit published
59
58.4%
Outside Waratek scope
1
1.0%
Not applicable
37
36.6%
Withdrawn CVE
0
0.0%
blocked by ARMR today
3
3.0%
partly blocked
0
0.0%
not blocked
98
97.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
3
3.0%
Working exploit published
0
0.0%
Proof of concept only
18
17.8%
Forecast only
0
0.0%
No public exploit
80
79.2%
split by
peak 69 / quarter
Q1 221
Protected by Waratek1
Critical1
blocked by ARMR today1
Proof of concept only1
Q2 221
Protected by Waratek1
Critical1
blocked by ARMR today1
Proof of concept only1
Q3 220
Q4 220
Q1 230
Q2 230
Q3 230
Q4 230
Q1 240
Q2 240
Q3 240
Q4 240
Q1 250
Q2 250
Q3 250
Q4 251
Mitigation candidate1
Critical1
not blocked1
Exploited1
Q1 260
Q2 263
No exploit published1
Not applicable2
Critical3
not blocked3
No public exploit3
Q3 2626
Protected by Waratek1
No exploit published12
Not applicable13
Critical26
blocked by ARMR today1
not blocked25
Proof of concept only9
No public exploit17
Q4 2669
No exploit published46
Outside Waratek scope1
Not applicable22
Critical69
not blocked69
Exploited2
Proof of concept only7
No public exploit60
Q2 22Q4 22Q2 23Q4 23Q2 24Q4 24Q2 25Q4 25Q2 26Q4 26
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2022-23305 | Critical | 2022-01-18 | Protected by Waratek | Proof of concept only | By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. 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. |