Oracle November 2026 patches cover 655 new security fixes announced in Oracle’s November 17 Critical Security Patch Update. The immediate job is to match installed products and builds to Oracle’s risk matrices, then obtain each product’s patch instructions; use the vulnerability intelligence platform for broader vulnerability triage. The affected versions in the advisory are not fixed release numbers.
Oracle’s counts describe different product families and can include the same CVE in more than one matrix. They should not be added to estimate unique flaws. The comparison below selects common enterprise deployments and the conditions that change patch priority.
Oracle November 2026 Patches: Product Decision Matrix
| Product and affected versions | Oracle matrix finding | First owner decision |
|---|---|---|
| WebLogic Server: 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, 15.1.1.0.0 | Fusion Middleware family: 71 new patches; 53 may be remotely exploitable without authentication. WebLogic CVE-2026-91569 scores 10.0 under CVSS 3.1. | Identify reachable WebLogic deployments and the affected component. Obtain the applicable Fusion Middleware patch. |
| Access Manager: 12.2.1.4.0, 14.1.2.1.0 | In the same Fusion Middleware family. Admin Console CVE-2026-114835 and Authentication Engine CVE-2026-91500 each score 10.0, with remote exploitation without authentication marked Yes. | Review console and authentication service reachability, then patch the affected installation. |
| Database Server: 19.3 through 19.33, 21.3 through 21.24, 23.4.0 through 23.26.4 | Seven new Database Server patches; three may be remotely exploitable without authentication. Three 9.9 entries in Oracle Text or RDBMS require Create Session. | Separate server installations from client-only installations, then check privileges and affected version ranges. |
| E-Business Suite: 12.2.3 through 12.2.15 | 71 new E-Business Suite patches; 19 may be remotely exploitable without authentication. Its Database and Fusion Middleware components require separate consideration. | Track the suite patch and its dependent Database and Middleware updates together. |
| MySQL Server: 8.4.0 through 8.4.13, 9.7.0 through 9.7.4, and 26.10; MySQL Cluster includes 8.0.0 through 8.0.50 | MySQL family: ten new patches; three may be remotely exploitable without authentication. CVE-2026-114952 affects client programs and scores 9.1. | Inventory Server and Cluster separately, including client programs, before selecting a patch package. |
Read each count as a product family total, not as a count for the one named product. For example, the 53 unauthenticated network cases belong to Fusion Middleware as a whole. Oracle also lists other affected products, including APEX, REST Data Services, Java SE and PeopleSoft. Check the full product list when matching your inventory.
Why Do The Preconditions Change Priority?
Oracle’s matrix labels whether a vulnerability may be remotely exploitable without authentication. That flag describes a possible path, not observed exploitation or a promise of remote code execution. WebLogic CVE-2026-91569 and Access Manager CVE-2026-114835 have a Yes flag, network attack vector, no required privileges and no user interaction in Oracle’s matrix.
By contrast, Database Server CVE-2026-114848 scores 9.9 but requires the Create Session privilege. A database reachable only by authorized sessions still needs a patch, yet its exposure differs from a reachable unauthenticated middleware service. Oracle says none of its seven Database Server patches apply to client-only installations without Database Server.
Use external attack surface management to reconcile internet-reachable services with the product inventory. This is our prioritization step based on Oracle’s network conditions. It does not determine whether any named CVE has been exploited.
What Should Owners Verify Before Scheduling Patches?
Start with product family, exact installed build, deployment role, exposed protocol and the owner of each service. Oracle’s version column names affected supported versions; it does not identify every fixed build. Use the patch availability document linked from Oracle’s advisory for the package and installation sequence.
- Match the deploymentRecord product, complete version, server or client role, and exposed service.
- Read the relevant matrix rowCheck CVE, authentication flag, required privilege, user interaction and affected versions.
- Schedule the vendor packageFollow Oracle’s product-specific patch availability and installation document.
- Verify after changeConfirm the installed patch and running build, then retest the service path.
- Review skipped cyclesCheck earlier Oracle advisories for fixes absent from this CSPU.
E-Business Suite illustrates why a suite-level ticket can be incomplete. Oracle explicitly recommends applying this update to the suite’s Database and Fusion Middleware components as well. Record those components as linked change items, with their own patch evidence and post-change checks.
If a patch window is delayed, Oracle says blocking a required network protocol or removing unneeded privileges may reduce risk. Test either change outside production first because Oracle warns it can break application function. Oracle does not treat either measure as a lasting replacement for its patches.
Does Oracle’s Warning Mean These CVEs Are Under Attack?
Oracle says it periodically receives reports of attempts against vulnerabilities for which patches were already available. That is a general warning about previously patched flaws. The advisory does not state that the CVEs in this November update are being exploited, so do not label the whole set an active campaign.
Brandefense Blackhole recorded 4,176 dark-chat posts mentioning Oracle from August 20 through November 18, 2026. This measures broad Oracle discussion, not posts about this specific update or distinct incidents. The count cannot confirm exploitation of any CVE in the advisory.
For longer-term tracking, place deployment evidence in a patch management process and rank exceptions through vulnerability prioritization. Oracle’s October patch update analysis is a useful reminder to review earlier cycles too. Missing an earlier patch cannot be resolved by assuming it appears in November’s matrix.
Frequently Asked Questions
Are all 655 Oracle November patches remote code execution fixes?
No. Oracle lists different components, scores and exploitation conditions. Its remotely exploitable without authentication flag does not by itself identify remote code execution.
Does a 9.9 Database Server score mean anyone can attack it?
No. Oracle's three 9.9 Database examples require Create Session. Check the affected server version, required privilege and deployment reachability.
Are the versions in the Oracle advisory fixed releases?
No. Oracle labels them affected supported versions. Use the linked patch availability document for the applicable package and installation instructions.
