Introduction
Oracle's November 2026 Critical Security Patch Update fixes a flaw in the Core component of WebLogic Server. An attacker with nothing more than HTTP reachability, and no credentials, can use it to modify or delete critical data and force a complete denial of service. The issue (CVE-2026-91469, CVSS 3.1 9.4) affects all four supported WebLogic release lines. WebLogic sits in the enterprise middle tier, brokering requests between clients and databases, enterprise information systems and mainframe applications, so the fix is worth scheduling into the next maintenance window.
This post is a brief summary of what Oracle and public trackers have disclosed as of 18 November 2026, what remains unknown, and how the fix is delivered.
Technical Information
What Oracle has disclosed
The official description places the bug in the Core component of Oracle WebLogic Server, part of Oracle Fusion Middleware. Oracle describes it as easily exploitable by an unauthenticated attacker with network access via HTTP, and its risk matrix answers Yes in the "Remote Exploit without Auth." column.
The published CVSS 3.1 vector is:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H
Broken down using FIRST's metric vocabulary:
- AV:N Attack vector: Network
- AC:L Attack complexity: Low
- PR:N Privileges required: None
- UI:N User interaction: None
- S:U Scope: Unchanged
- C:L Confidentiality: Low
- I:H Integrity: High
- A:H Availability: High
The low confidentiality rating does not make this a low-severity issue. The score lands in the CVSS Critical band (9.0 to 10.0) because the high integrity and availability impacts combine with an unauthenticated, low-complexity network vector. As FIRST notes, CVSS measures severity, not organizational risk, so weigh the score against how and where each WebLogic instance is exposed.
Documented impact
According to Oracle, a successful attack can result in:
- Unauthorized creation, deletion or modification access to critical data or all Oracle WebLogic Server accessible data
- Unauthorized read access to a subset of Oracle WebLogic Server accessible data
- The ability to cause a hang or frequently repeatable crash (complete DoS) of Oracle WebLogic Server
The official description does not state that the flaw yields arbitrary code execution or complete server takeover. We have not assumed either.
Attack flow, as far as the disclosure supports it
Oracle's public material supports only a high-level attack model:
- The attacker reaches a WebLogic Server HTTP listener over the network. Oracle states that an HTTP entry in its risk matrix also includes HTTPS, so a TLS listener is equally in scope.
- The attacker sends requests that reach the vulnerable Core functionality. No account, session or prior privilege is required, and no user needs to interact with anything.
- Depending on the request, the result is unauthorized data modification or deletion, limited data disclosure, or a hang or repeatable crash of the server.
Oracle has not disclosed the vulnerable endpoint or handler, HTTP method, request parameters, payload structure or internal execution sequence. For that reason we do not reconstruct exploitation requests here, and no narrow endpoint-based workaround can be derived from public information.
Root cause and weakness classification
The root cause is not public. NVD's weakness field for this CVE is empty, and Oracle has published no CWE, root cause or code-level description. VulDB separately labels the entry CWE-285 (Improper Authorization) and marks that label as confirmed in its own database, but no Oracle or NVD root cause explanation accompanies that classification. Any claim about what the patch changes inside WebLogic Core, such as added input validation, tighter deserialization filtering or stricter request handling, would be speculation until someone performs a patch diff analysis of the binaries.
HTTPS is not a fix
Oracle's general production hardening guide recommends restricting external traffic to HTTPS application traffic. That is sound baseline practice, but for this CVE it does not remove the attack surface, because Oracle's November advisory explicitly states that HTTP-listed vulnerabilities include HTTPS. A deployment that follows the HTTPS-only guidance can still expose the vulnerable protocol.
Exploitation status
As of 18 November 2026, we found no confirmed exploitation in the wild and no named threat actor:
- Rapid7 reports "In CISA KEV Catalogue: False", and VulDB also labels KEV as no.
- The infrastack.ai tracker reports "No reports of exploitation as of Nov 17" and "no PoC found".
- No target-specific indicators of compromise have been published.
- EPSS data is inconsistent: Rapid7 lists it as N/A, while VulDB displays 0.00000. Neither should be read as evidence of zero risk.
These are observations about public reporting, not proof that exploitation has not occurred.
Patch Information
Oracle fixed CVE-2026-91469 in its November 2026 Critical Security Patch Update (CSPU), released 17 November 2026.
How the fix is delivered
This is a closed-source vendor fix with no public commit, source diff, patch number or fixed version string to study. Oracle's machine-readable CSAF advisory contains a single vendor_fix remediation for this CVE, described as "Oracle customers with valid support contracts". It points to the Fusion Middleware Patch Availability Document CPU450 on My Oracle Support, which the public advisory also links. To obtain the patch binaries, sign in to My Oracle Support and use CPU450 to locate the WebLogic patch for your release line.
Release lines covered
The CSAF data lists these product IDs as known_affected, and each needs the CSPU patch:
- WebLogic 12.2.1.4.0:
P-5242V-12.2.1.4.0 - WebLogic 14.1.1.0.0:
P-5242V-14.1.1.0.0 - WebLogic 14.1.2.0.0:
P-5242V-14.1.2.0.0 - WebLogic 15.1.1.0.0:
P-5242V-15.1.1.0.0
The CSAF data contains no separate fixed version entries. The fix is a patch applied on top of each release rather than an upgrade to a new version number, so moving between the listed releases does not by itself resolve exposure.
Where the CSPU fits in Oracle's cycle
Oracle now ships security fixes in two forms:
- Critical Patch Updates (CPUs): quarterly and cumulative.
- CSPUs: smaller, targeted releases between CPUs. Oracle says CSPUs "complement Oracle's existing quarterly cumulative Critical Patch Updates."
This fix arrived one month after the October 2026 CPU, which fixed a different unauthenticated WebLogic Core HTTP flaw (CVE-2026-91323). It is a new fix, not a reissue of that one. Because this CSPU only covers fixes that are new in this cycle, Oracle advises customers who skipped earlier CPUs or CSPUs to go back through those advisories as well.
Other WebLogic fixes in the same release
The November Fusion Middleware risk matrix lists several more WebLogic CVEs fixed alongside this one: CVE-2026-91416, CVE-2026-91456, CVE-2026-91470, CVE-2026-91569, CVE-2026-91570, CVE-2026-91583 and CVE-2026-91585. Patching a WebLogic home with the November CSPU should cover all of them in one maintenance window.
Interim risk reduction
Oracle states that blocking the protocols required for an attack may reduce risk until patches are applied. It warns that this can break application functionality and does not correct the underlying problem, so such changes should be tested on systems outside production first. Oracle's production hardening guide also recommends connection filters and restricting incoming connections to expected front-end hosts or administration subnets. That is general hardening, not a demonstrated complete mitigation for this CVE. Neither measure should be treated as evidence that an affected installation is no longer vulnerable.
Affected Systems and Versions
Oracle lists the following supported releases of Oracle WebLogic Server (component: Core) as affected:
- 12.2.1.4.0
- 14.1.1.0.0
- 14.1.2.0.0
- 15.1.1.0.0
Vulnerable configuration: any of these releases where the WebLogic Server HTTP or HTTPS listener is reachable by an attacker over the network, without the November 2026 CSPU applied. Authentication on the application does not protect against this issue, since no privileges are required.
Older, unsupported releases are not listed, but that should not be read as assurance of safety. Oracle states that unsupported releases are not tested for the vulnerabilities addressed by its updates and recommends upgrading to supported versions.
Vendor Security History
Oracle runs a structured disclosure program: quarterly cumulative CPUs, targeted CSPUs between them, and Security Alerts for fixes considered too critical to wait for either scheduled channel. The weak point, as Oracle itself documents, is deployment lag. The November advisory states that Oracle continues to receive reports of malicious attempts against vulnerabilities for which patches already exist, and that some attackers have succeeded because customers had not applied available patches. That is a general statement about Oracle products, not evidence that CVE-2026-91469 has been exploited.
Relevant WebLogic history includes:
- CVE-2020-14750: On 3 November 2020, Singapore's Cyber Security Agency reported active exploitation of this unauthenticated HTTP vulnerability in WebLogic Server, associated with server takeover, and advised immediate installation of updates.
- CVE-2026-21962: On 24 August 2026, CISA added this vulnerability, affecting Oracle HTTP Server and the WebLogic Server Proxy Plugin, to its Known Exploited Vulnerabilities catalog based on evidence of active exploitation. It is a different vulnerability in a different component.
- CVE-2026-91323: A separate unauthenticated WebLogic Core HTTP flaw fixed in the October 2026 CPU, one month before this issue.
These cases show that WebLogic is a recurring target and that unauthenticated HTTP flaws in the product have been exploited before. They do not establish a shared mechanism, attacker population or outcome for CVE-2026-91469.
References
- NVD: CVE-2026-91469
- CVE Record: CVE-2026-91469
- Oracle Critical Security Patch Update Advisory, November 2026
- Oracle Critical Security Patch Update Advisory, November 2026 (verbose)
- Oracle CSAF advisory, November 2026
- My Oracle Support Patch Availability Document CPU450
- Oracle Critical Patch Updates, Critical Security Patch Updates, Security Alerts and Bulletins
- Rapid7 Vulnerability Database entry
- VulDB entry
- infrastack.ai tracker entry
- CISA Known Exploited Vulnerabilities Catalog (WebLogic search)
- CISA: Adds One Known Exploited Vulnerability to Catalog, 24 August 2026
- CERT Vanuatu Advisory 196
- Securing a Production Environment for Oracle WebLogic Server 15.1.1
- Configuring Security for a WebLogic Domain 14.1.1.0
- Announcing Oracle WebLogic Server and Coherence 15.1.1
- Oracle WebLogic Server product page
- TechTarget: What is WebLogic Server?
- FIRST CVSS v3.1 Specification Document
- FIRST CVSS v3.1 User Guide
- Cyber Security Agency of Singapore: RCE vulnerability in Oracle WebLogic Server (2020)



