Oracle released its November 2026 Critical Security Patch Update (CSPU) on 17 November 2026. Patch in this order: internet-facing Oracle Fusion Middleware (WebLogic Server, Access Manager and related products) first, then every Java runtime, then E-Business Suite and Database. The rest of this article shows how to find what you actually run and what to do if the patch window is days away.
This is a patch-prioritization guide, not an exploit write-up. It contains no exploit details, and none of the reported flaws is described beyond what Oracle and reputable outlets have published.
Who this is for and what you will have at the end
This guide is for sysadmins, security engineers and small IT teams who run any Oracle on-premises product or any Java application. If you only run a few Java desktop tools, skip to the Java section. By the end you will have a version inventory, a patch order, a list of stop-gap controls, and the dates of the next two Oracle releases.
A note on sourcing. Oracle's own advisory page returned HTTP 403 to automated fetches on 2026-11-18, so the figures below come from Oracle's text as quoted in search results and from third-party analyses, and they are labeled "reported" where they are not directly from Oracle. Open the advisory in a browser and compare before you commit change windows.
What Oracle released
Oracle's pre-release announcement for this update said it addresses 652 new security patches, and that the highest CVSS v3.1 base score for vulnerabilities in Oracle Fusion Middleware is 10.0. It listed Oracle Access Manager (12.2.1.4.0 and 14.1.2.1.0) among the affected Fusion Middleware products.
Security Boulevard's analysis of the final update reports 640 unique CVEs in 655 security updates across 21 Oracle product families. The difference between 640 and 655 is patches that share a CVE (15 in total). By severity it reports 62 critical, 249 high, 274 medium and 70 low patches.
The table lists the families most relevant to a patch order, with the patch count and the number Oracle marks as remotely exploitable without authentication (as reported by Security Boulevard).
| Product family | Patches | Remote, no authentication |
|---|---|---|
| Oracle Hyperion | 267 | 107 |
| Oracle Fusion Middleware | 71 | 53 |
| Oracle E-Business Suite | 71 | 19 |
| Oracle Java SE | 11 | 11 |
| Oracle Database Server | 7 | 3 |
| Oracle MySQL | 10 | 3 |
| Oracle REST Data Services | 8 | 5 |
| Oracle Enterprise Manager | 5 | 3 |
You will see claims elsewhere of six separate CVSS 10.0 flaws, with specific CVE numbers for WebLogic, Access Manager, Platform Security for Java and BI Enterprise Edition. We could not confirm those CVE numbers or that count from any page we could open, so this article does not repeat them. What is confirmed from Oracle's pre-release text is that the maximum Fusion Middleware score is 10.0. Check the risk matrices in the advisory for the exact list.
Patch order
Order by exposure first and by score second. A CVSS 10.0 on a server nobody can reach is less urgent than an 8.1 on something facing the internet.
Priority 1: internet-facing Fusion Middleware
Fusion Middleware has 71 patches, 53 of them remotely exploitable without authentication. Start with anything reachable from outside your network:
- WebLogic Server instances serving applications or exposing the administration console.
- Oracle Access Manager and other single sign-on components. If sign-on is compromised, everything behind it is.
- Oracle Platform Security for Java, which the advisory also lists (12.2.1.4.0 and 14.1.2.0.0 reported for the Java entries).
- Oracle BI and Analytics products if published to the internet.
Internal-only instances come next, in the same priority 1 window if you can, because an attacker who gets a foothold on a network will look for unpatched middleware.
Priority 2: every Java runtime
Oracle says all 11 Java SE fixes may be exploitable remotely over a network without credentials, with a highest CVSS 3.1 score of 8.1. The affected versions listed are 8u511 (including the perf build), 11.0.33, 17.0.21, 21.0.13, 25.0.5 and 27.0.1. JavaFX is listed for 21.0.13, 25.0.5 and 27.0.1, and GraalVM for JDK for 21.0.13.
Remote and unauthenticated usually means "applies when a Java program processes untrusted input, for example a server application", not "any PC with Java installed is exposed". Servers and build systems come before desktops.
Third-party builds matter too. Eclipse Temurin, Amazon Corretto, Azul Zulu and other OpenJDK distributions are built from the same source, so check each vendor's release notes for when they ship the equivalent fixes. We did not verify any vendor's fixed version numbers. Secondary reports mention builds such as 8u513 and 17.0.21.1, but no source we opened confirmed them, so take fixed version numbers only from Oracle or your vendor.
Priority 3: E-Business Suite and Database
E-Business Suite has 71 patches, 19 remotely exploitable without authentication. Database Server has 7 patches, 3 of them remote and unauthenticated. These are usually behind more layers of network control than middleware, which is why they come third, but E-Business Suite is often published to suppliers or the internet. If yours is, move it up.
Then work through the remaining families you own, including MySQL, REST Data Services and Enterprise Manager from the table.
Find out what you run
You cannot patch what you have not found. Run these on each host.
Java
java -versionThe first line shows the version, for example openjdk version "17.0.21" for an affected 17 build. Compare it to the affected list above. Also search for runtimes that are not on the PATH: application directories, containers, build agents, and products that bundle their own JRE. Ask vendors of bundled products when they will ship an updated runtime.
On Windows, list the Java executables found on the PATH with:
Get-Command java -All | Select-Object SourceThis does not find bundled copies, so also search the application folders.
WebLogic Server
Oracle's documentation on viewing release numbers runs the version class from the WebLogic jar:
java -cp $WL_HOME/server/lib/weblogic.jar weblogic.versionOn Windows use %WL_HOME%\server\lib\weblogic.jar. Per an Oracle support note (Doc ID 1676652.1, as summarized in search results), this can keep showing the base version after a patch set is applied, so confirm the patch level with OPatch as well.
OPatch inventory
Oracle's OPatch documentation says the ORACLE_HOME environment variable must be set to the Oracle home, and recommends the -detail option to confirm patches recorded in the inventory:
export ORACLE_HOME=/u01/app/oracle/product/middleware
$ORACLE_HOME/OPatch/opatch lsinventory -detailThe path above is an example; use your own Oracle home. Run it once per home and record the patch IDs. Then compare them against the patch IDs listed in the November advisory's patch availability information for your product and version.
If you cannot patch today
Patch windows for production middleware are rarely same-day. Until yours arrives:
- Block the WebLogic administration console and management ports from the internet. The console should be reachable only from a management network or VPN.
- Restrict network access to Oracle application ports to the clients that need them, using firewall rules or security groups.
- Put internet-facing applications behind a web application firewall. A WAF reduces exposure to some attack patterns but does not replace the patch.
- Turn on and review access logs for the administration and sign-on components, and alert on unusual requests.
- Make a backup or snapshot before patching so you can roll back.
These are compensating controls. Write down who owns the exception and the date it ends.
About "Java4Shell" (CVE-2026-114938)
Several outlets use the nickname Java4Shell for CVE-2026-114938, and the reporting conflicts:
- Security Boulevard says Oracle patched CVE-2026-114938 in the Compiler component of Java SE and GraalVM, CVSS 3.1 score 8.1, and that technical details are expected soon.
- Other outlets say Oracle has not tied the CVE to any of its 11 fixes, and that researchers dispute whether it is remote code execution or only a JVM crash.
We could not resolve this from sources we could open. The practical advice is the same either way: install the November Java updates and do not wait for the argument to settle. Re-check the advisory later, because details are often revised after release.
Patch calendar
Oracle publishes a Critical Patch Update (CPU) in January, April, July and October, and Critical Security Patch Updates (CSPU) in the other months it releases, on the third Tuesday. As seen on 2026-11-18:
| Release | Date |
|---|---|
| Next CSPU | 15 December 2026 |
| Next CPU | 19 January 2027 |
| Following CSPU | 16 February 2027 |
Oracle also publishes a pre-release announcement on the Thursday before each CSPU. Pages cached at different times showed slightly different "next dates", so confirm on Oracle's security-alerts page before you book change windows.
Troubleshooting
opatch lsinventoryfails. Oracle Support has notes on failures such as error code 255 after an OPatch upgrade (Doc ID 2794973.1) and after applying a recommended WebLogic patch bundle (Doc ID 2769688.1). Check that ORACLE_HOME is set and the central inventory is not damaged, and open the notes on My Oracle Support.weblogic.versionshows the old number after patching. See the caveat above and use OPatch for the real patch level.- Several WebLogic versions on one host. Oracle Support note 2755130.1 covers setting ORACLE_HOME explicitly before running the version command.
- A product bundles an old Java. Updating the system Java does not change it. Wait for the vendor's update or follow the vendor's documented way to point the product at a patched runtime.
What we checked
- Searched for Oracle's November 2026 CSPU on 2026-11-18. Oracle's pre-release announcement, as quoted in search results, states 652 new patches and a maximum Fusion Middleware CVSS v3.1 score of 10.0, and lists Oracle Access Manager 12.2.1.4.0 and 14.1.2.1.0.
- Opened Security Boulevard's analysis on 2026-11-18: 640 unique CVEs, 655 security updates, 21 product families. We recalculated: the severity counts 62 + 249 + 274 + 70 = 655, the 21 family patch counts also sum to 655, and 655 - 640 = 15 patches that share a CVE.
- Opened a Java analysis (pbxscience.com) on 2026-11-18 and compared it with the Security Boulevard family table: both give 11 Java SE fixes, all remote without authentication, and the affected versions 8u511, 11.0.33, 17.0.21, 21.0.13, 25.0.5 and 27.0.1.
- Compared the Java4Shell claim across several outlets and found they conflict (patched, 8.1 per Security Boulevard; not tied to Oracle's fixes per Cybersecurity News; disputed per The Hacker News as syndicated). We report the conflict instead of choosing a side.
- Searched for the six CVSS 10.0 CVE numbers circulating in other coverage and could not confirm them, so we left them out.
- Checked the syntax of
weblogic.versionandopatch lsinventory -detailagainst Oracle documentation excerpts, including the ORACLE_HOME requirement. - Not checked hands-on: Oracle's advisory returned HTTP 403, none of these commands were executed on a live system, and we did not verify fixed version numbers for any vendor.
Last tested: 2026-11-18
References
- Oracle Critical Security Patch Update advisory, November 2026: https://www.oracle.com/security-alerts/cspunov2026.html
- Oracle security alerts and schedule: https://www.oracle.com/security-alerts/
- Security Boulevard, Oracle November 2026 CSPU analysis: https://securityboulevard.com/2026/11/oracle-november-2026-critical-security-patch-update-addresses-640-cves-cve-2026-114938/
- PBX Science, Oracle's November 2026 Java update: https://pbxscience.com/oracles-november-2026-java-update-11-java-se-fixes-all-potentially-exploitable-without-authentication/
- Cybersecurity News on the Java 17 report: https://cybersecuritynews.com/java-17-rce-vulnerability/
- Oracle, viewing Fusion Middleware release numbers: https://docs.oracle.com/en/middleware/fusion-middleware/12.2.1.4/asadm/viewing-release-numbers2.html
- Oracle, OPatch syntax and commands: https://docs.oracle.com/en/enterprise-manager/cloud-control/enterprise-manager-cloud-control/13.4/optch/opatch-syntax-and-commands.html
Comments
Questions and tips are welcome. Comments are checked by the EpiFive team before they appear; please do not share passwords, phone numbers or other private details.