Oracle Critical Patch Update October 2025
Released October 2025 · Oracle's advisory ↗ · ← Critical Patch Update, July 2025 · Critical Patch Update, January 2026 →
234 CVEs in this release, one square each
By status
13Protected by Waratek5Mitigation candidate86No exploit published4Outside Waratek scope126Not applicable
7Exploited, marked by the ring
No exploit published. For 39 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 103 matches · 44 in Waratek scope · 11 protected · 2 exploited · 1 CISA KEV · 7 public PoC · 6 EPSS ≥ 0.5
103matches
44in Waratek scope42.7%
11protected10.7%
2exploited1.9%
1CISA KEV1.0%
7public PoC6.8%
6EPSS ≥ 0.55.8%
Protected by Waratek
11
10.7%
Rule in development
0
0.0%
Mitigation candidate
2
1.9%
No exploit published
31
30.1%
Outside Waratek scope
3
2.9%
Not applicable
56
54.4%
Withdrawn CVE
0
0.0%
blocked by ARMR today
11
10.7%
partly blocked
0
0.0%
not blocked
92
89.3%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 43 / quarter
Q4 203
Protected by Waratek2
No exploit published1
Medium3
blocked by ARMR today2
not blocked1
No public exploit3
Q1 211
No exploit published1
High1
not blocked1
No public exploit1
Q2 212
No exploit published1
Not applicable1
High1
Medium1
not blocked2
Proof of concept only1
Forecast only1
Q3 212
Not applicable2
Critical1
High1
not blocked2
Forecast only1
No public exploit1
Q4 210
Q1 221
No exploit published1
Medium1
not blocked1
No public exploit1
Q2 222
Protected by Waratek1
No exploit published1
High1
Medium1
blocked by ARMR today1
not blocked1
No public exploit2
Q3 220
Q4 220
Q1 230
Q2 236
No exploit published1
Not applicable5
High1
Medium5
not blocked6
Proof of concept only1
No public exploit5
Q3 230
Q4 233
No exploit published2
Not applicable1
Critical1
High1
Medium1
not blocked3
No public exploit3
Q1 242
Outside Waratek scope1
Not applicable1
Critical1
Medium1
not blocked2
Proof of concept only1
No public exploit1
Q2 245
Not applicable5
Critical1
High2
Medium2
not blocked5
Forecast only1
No public exploit4
Q3 246
No exploit published2
Not applicable4
High2
Medium4
not blocked6
Proof of concept only1
No public exploit5
Q4 2411
Protected by Waratek3
No exploit published4
Outside Waratek scope1
Not applicable3
Critical3
High4
Medium4
blocked by ARMR today3
not blocked8
Working exploit published1
No public exploit10
Q1 2516
Protected by Waratek2
No exploit published5
Not applicable9
Critical1
High9
Medium5
Low1
blocked by ARMR today2
not blocked14
Exploited1
Proof of concept only3
No public exploit12
Q2 2543
Protected by Waratek3
Mitigation candidate2
No exploit published12
Outside Waratek scope1
Not applicable25
Critical4
High22
Medium15
Low2
blocked by ARMR today3
not blocked40
Exploited1
Working exploit published2
Proof of concept only12
No public exploit28
Q4 20Q2 21Q4 21Q2 22Q4 22Q2 23Q4 23Q2 24Q4 24Q2 25
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| 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. |
| CVE-2020-13956 | Medium | 2020-12-02 | No exploit published | No public exploit | Apache HttpClient versions prior to version 4.5.13 and 5.0.3 can misinterpret malformed authority component in request URIs passed to the library as java.net.URI object and pick the wrong target host for request execution. |
| CVE-2020-15250 | Medium | 2020-10-12 | Protected by Waratek | No public exploit | In JUnit4 from version 4.7 and before 4.13.1, the test rule TemporaryFolder contains a local information disclosure vulnerability. On Unix like systems, the system's temporary directory is shared between all users on that system. Because of this, when files and directories are written into this directory they are, by default, readable by other users on that same system. This vulnerability does not allow other users to overwrite the contents of these directories or files. This is purely an information disclosure vulnerability. This vulnerability impacts you if the JUnit tests write sensitive information, like API keys or passwords, into the temporary folder, and the JUnit tests execute in an environment where the OS has other untrusted users. Because certain JDK file system APIs were only added in JDK 1.7, this this fix is dependent upon the version of the JDK you are using. For Java 1.7 and higher users: this vulnerability is fixed in 4.13.1. For Java 1.6 and lower users: no patch is available, you must use the workaround below. If you are unable to patch, or are stuck running on Java 1.6, specifying the `java.io.tmpdir` system environment variable to a directory that is exclusively owned by the executing user will fix this vulnerability. For more information, including an example of vulnerable code, see the referenced GitHub Security Advisory. |