Introduction
Oracle's November 2026 Critical Security Patch Update fixes a flaw in WebLogic Server that lets an unauthenticated attacker with T3 or IIOP network access take over the server. Because the bug needs no credentials and no user interaction, and because WebLogic commonly hosts enterprise Java applications, Oracle scored it 9.8 under CVSS 3.1.
This post summarizes what the public record says about CVE-2026-91470, what Oracle has shipped to fix it, and where the disclosure stops. The supplied CVE record lists the vendor as Unknown and has no CWE. The vendor is Oracle Corporation, and NVD now lists CWE-306, Missing Authentication for Critical Function, with CISA ADP shown as the source.
Technical information
What the record establishes
Oracle's CVE record and its November risk matrix agree on the core facts:
- Vendor: Oracle Corporation
- Product: Oracle WebLogic Server, part of Oracle Fusion Middleware
- Component: Core
- Entry protocols: T3 and IIOP
- Authentication required: None
- Documented outcome: Takeover of Oracle WebLogic Server
- Severity: Oracle CNA CVSS 3.1 base score 9.8, Critical
- Weakness classification (NVD): CWE-306, Missing Authentication for Critical Function
- Published: November 17, 2026
Reading the CVSS vector
The published vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Broken down:
- AV:N: reachable over the network
- AC:L: low attack complexity; Oracle calls it easily exploitable
- PR:N: no privileges required
- UI:N: no user interaction required
- S:U: scope unchanged
- C:H / I:H / A:H: high impact to confidentiality, integrity and availability
The score is a severity assessment. It is not evidence that a working exploit exists. FIRST's CVSS v3.1 specification separates intrinsic Base metrics from Temporal characteristics such as exploit maturity, so the 9.8 does not by itself say anything about attacker activity.
Root cause: what CWE-306 tells us, and what it does not
The only root-cause signal in the public record is NVD's CWE-306 classification. Read alongside Oracle's statement that the flaw is reachable without authentication over T3 and IIOP, it suggests that some sensitive operation in the Core component could be reached through those protocols without an authentication check, and that the fix adds one. That is an inference from the CWE label. Oracle has not confirmed it.
WebLogic is closed source, and Oracle has not published technical details beyond the risk matrix entry. The reviewed records do not disclose:
- the affected function or class
- the request structure or payload
- the exploitation sequence
- the specific code defect
There is no public commit, diff or vulnerable code snippet to examine. Given WebLogic's history with T3 and IIOP, it is tempting to assume insecure deserialization and a gadget chain. Neither is established for this CVE, and neither is operating system privilege escalation or compromise of systems beyond WebLogic itself. The defensible impact statement is Oracle's: WebLogic Server takeover with high confidentiality, integrity and availability impact.
Attack flow as documented
Based only on what Oracle and NVD publish, the attack path looks like this:
- Reach a T3 or IIOP listener. The attacker needs network access to a WebLogic instance that accepts T3 or IIOP. Oracle's WebLogic 15.1.1 lockdown guidance warns that enabling tunneling on an externally available channel lets an external client send T3 or IIOP traffic, so an apparently HTTPS-facing deployment may still expose these protocols.
- Interact with the vulnerable Core functionality without credentials. No account, session or user action is required.
- Take over the server, which Oracle documents as the result of successful exploitation.
Exposure decisions should therefore rest on the named versions and on whether T3 or IIOP is reachable, not on assumptions about a particular exploit implementation.
Exploitation status
As of November 18, 2026, the reviewed sources do not establish active exploitation or identify a responsible actor:
- Rapid7 lists the CISA KEV status as false and EPSS as N/A.
- StackFlag, updated November 18, states the vulnerability is not known to be exploited.
- No verified public exploit or proof of concept was identified.
- No CVE-specific indicators of compromise were identified.
These are reporting signals, not proof that attacks have not happened, and the status can change as evidence develops.
Patch information
The fix ships in Oracle's November 2026 Critical Security Patch Update (CSPU). Oracle published the advisory on November 17, 2026 as Rev 1. In the Fusion Middleware risk matrix, the bug is listed under Oracle WebLogic Server, component Core:
- Protocols: T3, IIOP
- Remotely exploitable without auth: Yes
- CVSS 3.1: 9.8 (
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) - Patched release lines: 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, 15.1.1.0.0
All four supported WebLogic release lines receive a fix. NVD lists only this Oracle advisory as its reference.
Where the patch comes from
The advisory does not link directly to a download. It points to the Fusion Middleware Patch Availability Document (PAD) on My Oracle Support, documentId=CPU450, which maps each WebLogic version to its patch numbers and provides installation instructions. One upstream source named CPU433 instead, but the advisory itself links to CPU450. Under Oracle's Security Fixing Policies, CSPU fixes are available to active Oracle Support customers through My Oracle Support, so the patch binaries and the WebLogic patch numbers inside the PAD are not public. We are not listing specific patch numbers or commands for that reason.
How CSPUs fit the release cycle
CSPUs started in June 2026. They are monthly, targeted releases for critical bugs, published on the third Tuesday of months without a quarterly Critical Patch Update (CPU). Oracle says quarterly CPUs remain cumulative and include every fix from earlier CSPUs, so this fix should also land in the next quarterly CPU, which on Oracle's schedule is January 2027. For teams that only patch quarterly, the November CSPU is the earliest way to get the fix, not the only one.
Interim containment while patching
Oracle's advisory says blocking the network protocols required by an attack may reduce risk until patching is complete, and explicitly warns that this does not correct the underlying vulnerability. Oracle's WebLogic hardening documentation describes the relevant controls:
- Restrict external protocols: use network channels and firewalls to allow only HTTPS application traffic externally, and block external T3, T3s, IIOP and IIOPs traffic.
- Separate internal channels: make internal channels for other protocols reachable only from trusted client IP addresses.
- Disable tunneling on external channels: tunneling can carry T3 or IIOP traffic over an otherwise HTTP channel.
- Use connection filters carefully: filters can match on protocol, network address or DNS node name, but Oracle's connection filter documentation notes that the first matching rule wins and an unmatched connection is permitted. A configured filter is not proof that unwanted access is denied.
Oracle warns that these changes can break application functionality and recommends testing them on nonproduction systems first. Treat them as temporary containment alongside the patch, not as a replacement for it.
Affected systems and versions
Oracle lists the following supported versions of Oracle WebLogic Server as affected:
- 12.2.1.4.0
- 14.1.1.0.0
- 14.1.2.0.0
- 15.1.1.0.0
The vulnerable configuration is any of these versions where an attacker can reach the server over T3 or IIOP, including cases where those protocols are tunneled over an externally available channel.
Oracle also notes that releases outside Premier Support or Extended Support are not tested for the vulnerabilities addressed in a patch update. An older release's absence from this list should therefore not be read as evidence that it is unaffected; Oracle recommends upgrading to supported releases.
Vendor security history
WebLogic has a documented history of unauthenticated remote vulnerabilities attracting attackers. On April 26, 2019, Oracle issued an emergency security alert for CVE-2019-2725, a WebLogic flaw in Web Services over HTTP that was remotely exploitable without authentication. On April 28, 2019, Unit 42 reported a Muhstik Linux botnet variant exploiting it in the wild, capturing exploit traffic from three new samples. Unit 42 described cryptocurrency mining and DDoS as typical Muhstik activity after compromise, and confirmed that Oracle's emergency patch protected against that botnet version.
That case is a different vulnerability in a different component, delivered over a different protocol. No evidence we reviewed links Muhstik, or any named actor, to CVE-2026-91470. It does show both sustained attacker interest in WebLogic and a vendor fix that held up against an observed campaign.
On the process side, Oracle publishes advisories, risk matrices and Patch Availability Documents, and its Security Fixing Policies reserve the option to ship patches or workaround instructions outside the normal schedule for particularly critical vulnerabilities or reported active exploitation. The November 2026 advisory also repeats a general warning that attackers have succeeded against Oracle customers who did not apply available patches. Patch availability and patch deployment are separate outcomes.
References
- NVD: CVE-2026-91470
- NVD: CVE-2026-91470 (patch source link)
- CVE Record: CVE-2026-91470
- Oracle Critical Security Patch Update Advisory, November 2026
- Text Form of Oracle CSPU November 2026 Risk Matrices
- Oracle Security Fixing Policies
- November 2026 Critical Security Patch Update Released, Oracle Security Blog
- infrastack.ai: CVE-2026-91470
- Rapid7 Vulnerability Database: CVE-2026-91470
- StackFlag: CVE-2026-91470
- Oracle: Lock Down WebLogic Server (15.1.1)
- Oracle: Using Network Connection Filters (12.2.1.3)
- Oracle: Configuring Security for a WebLogic Domain (14.1.1.0)
- Oracle WebLogic Server Technical Information
- About Oracle, Company Information
- FIRST: CVSS v3.1 Specification Document
- CISA Known Exploited Vulnerabilities Catalog
- Oracle Security Alert CVE-2019-2725
- Unit 42: Muhstik Botnet Exploits the Latest WebLogic Vulnerability



