Introduction
Oracle's November 2026 Critical Security Patch Update (CSPU) fixes a flaw in the TopLink Integration component of Oracle WebLogic Server that, according to Oracle, lets an unauthenticated attacker with HTTP network access take over the server. Every supported WebLogic release line Oracle lists is affected, and the issue carries a CVSS 3.1 base score of 9.8, which puts it at the front of the patch queue for teams running WebLogic.
Oracle WebLogic Server is Oracle's platform for developing, deploying and running enterprise Java applications on premises and in the cloud, with Kubernetes support and integration across Oracle's product portfolio. Enlyft counts 12,593 companies using WebLogic (about 0.5% of its Application Servers category), while W3Techs detects it on less than 0.1% of websites whose web server it knows. These figures measure different populations and say nothing about how many instances are vulnerable. As the application server layer of Oracle Fusion Middleware, WebLogic runs the Java workloads deployed on it, so a compromise of the server extends to those applications.
Technical information
What Oracle has disclosed
The authoritative technical description is Oracle's Fusion Middleware risk matrix in the November 2026 CSPU. It records the following for CVE-2026-91570:
- Product: Oracle WebLogic Server (Oracle Fusion Middleware)
- Component: TopLink Integration
- Protocol: HTTP
- Remotely exploitable without authentication: Yes
- CVSS 3.1 base score: 9.8 (Critical)
- Stated outcome: takeover of Oracle WebLogic Server
The published vector is:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Read against the FIRST CVSS v3.1 specification, this means network attack vector, low attack complexity, no privileges required, no user interaction, unchanged scope, and high impact to confidentiality, integrity and availability. The Base group describes intrinsic characteristics of the vulnerability. It is a severity statement, not a measure of observed attack activity.
Root cause: what is and is not known
The structured CVE record classifies the weakness as CWE 306, Missing Authentication for Critical Function. VulDB labels it differently, as CWE 269 (privileges management). We treat the structured record as the more direct basis for the weakness label, but neither classification describes an implementation.
The NVD feed data we started from also had a data quality gap. It listed the vendor as Unknown and the CWE as None, while the structured record identifies the vendor as Oracle Corporation and includes CWE 306.
Beyond the classification, the public record is thin by design:
- WebLogic is closed source, so there is no public commit, diff or changelog showing which TopLink Integration code path changed.
- Oracle has not published the root cause or the specific classes it modified.
- No vulnerable endpoint, HTTP method, parameter, payload or configuration prerequisite beyond network access is disclosed.
- Public sources do not establish deserialization, SQL injection or any particular code execution technique.
- Oracle's disclosure policy states that it does not distribute exploit or proof-of-concept code, so the absence of Oracle-published exploit detail is expected and is not evidence that exploitation is hard.
Any write-up claiming to show the exact code change is speculation until someone diffs the patched binaries. The CSPU is the fix of record and the risk matrix is the only authoritative technical description.
Attack flow based on the public record
Without a published root cause, the attack flow can only be stated at the level the advisory and vector support:
- The attacker identifies a WebLogic Server instance running one of the affected releases and has network access to it over HTTP.
- The attacker sends HTTP traffic that reaches functionality in the TopLink Integration component. No credentials are needed (PR:N), no user has to take any action (UI:N), and Oracle describes the issue as easily exploitable (AC:L).
- Consistent with the CWE 306 classification, the targeted function performs a critical operation without first requiring authentication.
- Successful exploitation results in takeover of the WebLogic Server, with high impact to confidentiality, integrity and availability within the server's own security scope (S:U).
The specific request that drives step 2 has not been published.
Exploitation status
As of 18 November 2026:
- StackFlag (updated 18 November) reports the CVE as "Not known to be exploited."
- Rapid7 reports that it is not in the CISA KEV catalog and lists EPSS score and percentile as N/A, not zero.
- TheHackerWire reports "No Public PoC Detected", a secondary-source assessment.
- No threat actor, malware family or indicator set is associated with this CVE in the reviewed reporting.
These are bounded statements about current reporting, not proof that exploitation has not occurred. We would not describe this issue as an actively exploited zero day on the available evidence.
Patch information
Where the fix lives
Oracle fixed CVE-2026-91570 in the November 2026 Critical Security Patch Update, published on 17 November 2026 as Rev 1 (initial release). The Fusion Middleware risk matrix lists the CVE under Oracle WebLogic Server, component TopLink Integration, protocol HTTP, remotely exploitable without authentication, and lists four supported release lines as affected and needing the patch: 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0 and 15.1.1.0.0. Oracle's advisory strongly recommends applying security patches without delay.
How to get and apply the patch
The advisory does not link to downloads directly. Its Patch Availability Document column points WebLogic customers to the Fusion Middleware patch availability document on My Oracle Support (documentId=CPU450), which maps each affected release to its patch number and contains the installation instructions. For the full history of CSPU and CPU patches for Fusion Middleware products, Oracle points to My Oracle Support Doc ID KA1182. A support contract is required to download patches.
In practice:
- Find your exact WebLogic release (for example 14.1.2.0.0).
- Open the Fusion Middleware patch availability document for November 2026 and select the WebLogic Server patch for that release.
- Apply it with OPatch, following the README.
- Check the inventory to confirm the November 2026 patch ID is installed on every node in the domain, including Administration and Managed Servers:
opatch lsinventory
Related TopLink Integration fixes
The same risk matrix lists three more WebLogic TopLink Integration CVEs: CVE-2026-91569, CVE-2026-91583 and CVE-2026-91585. They are separate advisory entries but share the component and the release vehicle. If you run TopLink- or EclipseLink-backed WebLogic deployments, plan to apply the full November 2026 WebLogic patch for your release rather than looking for a fix for CVE-2026-91570 alone.
Conflicting "no fix" reports
Several third-party CVE trackers still show this CVE as unpatched. SecurityOnline's CVE Watchtower page, for example, says no patched version has been published. These pages were generated from the bare CVE record, which carries no fixed version data, and some show a last modified date earlier than the 17 November release. StackFlag similarly notes that the CVE record does not list a fixed version. Oracle's advisory and risk matrix take precedence. A vendor patch exists and has been released.
Interim risk reduction
Where patching cannot happen immediately, Oracle's advisory notes that blocking the network protocols required by an attack may reduce risk. For this CVE that protocol is HTTP. Oracle also warns that this can break application functionality, does not correct the underlying vulnerability, is not a long-term solution, and should be tested on nonproduction systems first.
Oracle's WebLogic lockdown guidance additionally recommends firewalls and WebLogic connection filters so that externally exposed ports accept connections only from expected frontend hosts and administrative traffic only from expected subnets. This is general hardening, not a CVE-specific fix.
WebLogic Server for OCI
Oracle's WebLogic Server for OCI documentation states that existing domains do not automatically receive patches from new releases. Administrators must apply them manually. Oracle documents a patching utility that can list, download, apply and roll back patches, and the administration server's Monitoring page and Patch List can be used to identify the deployed WebLogic version. Do not assume a new service release has updated an existing domain.
Affected systems and versions
Oracle lists the following supported Oracle WebLogic Server releases as affected:
- 12.2.1.4.0
- 14.1.1.0.0
- 14.1.2.0.0
- 15.1.1.0.0
The affected component is TopLink Integration, reachable over HTTP without authentication. No additional configuration prerequisite is published.
Some additional scoping notes:
- Oracle states that unsupported releases are not tested against the vulnerabilities addressed by its updates and that earlier releases may also be affected. Absence from the list is not a statement that an older release is safe, and Oracle recommends moving unsupported deployments to supported releases.
- Upgrading to one of the listed releases does not by itself remediate the issue. The November 2026 patch must be applied.
- Existing WebLogic Server for OCI domains require manual patching, as described above.
- Deployments using TopLink Integration should also account for CVE-2026-91569, CVE-2026-91583 and CVE-2026-91585, fixed in the same update.
Vendor security history
Oracle ships quarterly cumulative Critical Patch Updates and complements them with CSPUs, which it describes as targeted, high-priority security fixes. Its disclosure policy provides vulnerability specifics through advisories, release and installation notes, README files and FAQs, and explicitly excludes exploit or proof-of-concept code.
WebLogic has a documented record of real-world exploitation in other components:
- CVE-2019-2725 (wls9 async): Oracle released an emergency patch on 26 April 2019. Unit 42 documented a new Muhstik botnet variant exploiting the flaw on 28 April 2019 to install itself on vulnerable WebLogic systems, typically followed by cryptocurrency mining and DDoS activity. Unit 42 confirmed that Oracle's patch protected against the observed variant.
- CVE-2026-21962 (Oracle HTTP Server and WebLogic Server Proxy Plugin): Singapore's Cyber Security Agency reported a CVSS 10.0 score, Oracle security updates, active exploitation and a public proof of concept. CISA added it to the KEV catalog on 24 August 2026, without naming an actor in its alert.
These cases show that attackers do target Oracle middleware and that patch availability and active exploitation can coexist. They involve different components and do not indicate that the payloads, infrastructure or techniques apply to the TopLink Integration issue in CVE-2026-91570.
References
- NVD entry for CVE-2026-91570
- CVE Record: CVE-2026-91570
- CVE Services structured record (cveawg.mitre.org)
- Oracle Critical Security Patch Update Advisory, November 2026
- Text Form of Oracle CSPU November 2026 Risk Matrices
- Oracle Security Blog: November 2026 Critical Security Patch Update Released
- SecurityOnline CVE Watchtower: CVE-2026-91570
- StackFlag: CVE-2026-91570, Oracle WebLogic Server can be taken over remotely
- Rapid7 Vulnerability Database: CVE-2026-91570
- TheHackerWire: CVE-2026-91570 exploit status and fix
- VulDB: Oracle WebLogic Server TopLink Integration privileges management
- Oracle Vulnerability Disclosure Policies
- Oracle WebLogic Server for OCI: Patches
- Oracle: Lock Down WebLogic Server (15.1.1)
- Oracle WebLogic Server product page
- Oracle WebLogic Server Technical Information
- Unit 42: Muhstik Botnet Exploits the Latest WebLogic Vulnerability for Cryptomining and DDoS Attacks
- Cyber Security Agency of Singapore: Active Exploitation of Vulnerability in Oracle HTTP Server and Oracle WebLogic Server Proxy Plugin
- CISA Adds One Known Exploited Vulnerability to Catalog (24 August 2026)
- CISA Known Exploited Vulnerabilities Catalog (Oracle entries)
- FIRST CVSS v3.1 Specification Document
- Enlyft: Oracle WebLogic market share in Application Servers
- W3Techs: Usage Statistics and Market Share of WebLogic, November 2026
- Gartner Peer Insights: WebLogic Server Reviews and Ratings 2026



