Automated Threat Modeling

Brief Summary: Oracle WebLogic Server CVE-2026-91456, an Unauthenticated SOAP Takeover in the Core Component

A brief summary of CVE-2026-91456, a CVSS 9.8 flaw in the Core component of Oracle WebLogic Server that lets an unauthenticated attacker with network access over SOAP take over the server. The post covers affected releases, the November 2026 CSPU patch pathway through CPU450, and what the public record does and does not establish.

CVE Analysis

7 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-17

Brief Summary: Oracle WebLogic Server CVE-2026-91456, an Unauthenticated SOAP Takeover in the Core Component

Introduction

Oracle's November 2026 Critical Security Patch Update fixes a flaw in the Core component of WebLogic Server that lets an unauthenticated attacker with network access over SOAP take over the server. WebLogic provides the core runtime for Oracle Fusion Middleware, Oracle Applications and many Oracle Cloud services, so a 9.8-rated takeover condition in its Core component deserves prompt attention from anyone running the affected release lines.

The CVE data supplied to us listed the vendor as "Unknown". The CVE Program record identifies the vendor as Oracle Corporation and the product as Oracle WebLogic Server, part of Oracle Fusion Middleware.

Technical information

What Oracle has disclosed

Oracle's CSPU risk matrix places CVE-2026-91456 under Oracle Fusion Middleware, product Oracle WebLogic Server, component Core. The listed attack protocol is SOAP, and the issue is remotely exploitable without authentication. Oracle's description reads, in part, that this "easily exploitable vulnerability allows unauthenticated attacker with network access via SOAP to compromise Oracle WebLogic Server" and that "successful attacks of this vulnerability can result in takeover of Oracle WebLogic Server." Oracle's machine-readable CSAF advisory independently repeats these conditions and the affected releases.

Root cause: what is and is not known

This is a closed-source fix. Oracle has not published a commit, a diff or a technical root cause writeup, so the only window into the defect is Oracle's own advisory material. Specifically:

  • The public record does not disclose the vulnerable method, the request endpoint, the payload structure or the exploitation chain.
  • A later view of the NVD record displays CWE-287, Improper Authentication. The CVE Program record does not provide a CWE classification. The CWE label is a categorization, not a disclosure of the precise implementation defect.
  • NVD itself lagged behind Oracle. In one check NVD returned "CVE ID Not Found" for this identifier. The briefing later records an NVD entry published 17 November 2026 and modified 18 November 2026. Oracle's advisory is the authority for the fix.

We are not going to speculate about which historical WebLogic exploit family this resembles. The record supports a narrower conclusion: this is a critical, unauthenticated, SOAP-reachable takeover in the Core component.

CVSS breakdown

The published vector is:

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • AV:N (Attack Vector: Network): reachable remotely.
  • AC:L (Attack Complexity: Low): no special conditions are required.
  • PR:N (Privileges Required: None): no account is needed.
  • UI:N (User Interaction: None): no victim action is needed.
  • S:U (Scope: Unchanged): affected resources stay under the same security authority. This does not mean the consequences are minor.
  • C:H / I:H / A:H: high impact to confidentiality, integrity and availability.

These values produce the 9.8 base score. Per FIRST's CVSS framework, base severity is intrinsic to the vulnerability and separate from exploit maturity, so a high base score is not by itself evidence of an attack campaign.

Attack flow, as far as the public record supports it

Based on Oracle's published attack conditions, the exploitation path looks like this at a high level:

  1. The attacker has network access to a WebLogic Server instance running an affected release, over a path where SOAP is reachable.
  2. The attacker interacts with the server via SOAP without supplying any credentials (PR:N) and without needing any user to act (UI:N).
  3. Exploitation requires no special conditions (AC:L).
  4. Successful exploitation results in takeover of the WebLogic Server, with high impact to confidentiality, integrity and availability.

That is where the public record stops. Server takeover is the vendor-stated outcome. The available description does not establish specific operating system command execution techniques, persistence mechanisms or lateral movement capabilities. No public proof of concept, exploit request or indicator of compromise has been identified.

Exploitation status

Active exploitation is not confirmed, and no threat actor is attributed. The secondary tracker StackFlag lists the CVE as not known to be exploited, which is different from proof that it has never been exploited. A retrieved CISA KEV feed snapshot (catalog version 2026.11.17, released 17 November 2026 at 17:53:15.5664 UTC) did not establish an entry for this CVE, but that representation was incomplete, so KEV status should be treated as unconfirmed rather than absent.

Patch information

Oracle fixed CVE-2026-91456 in its November 2026 Critical Security Patch Update (CSPU), published 17 November 2026 (Rev 1, initial release). Every supported release line is affected, and each receives a patch in that CSPU:

  • 12.2.1.4.0
  • 14.1.1.0.0
  • 14.1.2.0.0
  • 15.1.1.0.0

How the fix is delivered

Oracle's CSAF advisory (cspunov2026csaf.json) carries a single remediation for this CVE: a vendor_fix that applies to "Oracle customers with valid support contracts" and points to the My Oracle Support Fusion Middleware Patch Availability Document, CPU450.

The four releases are marked known_affected, and the CSAF contains no fixed product entries. In practice, you apply a patch on top of your existing 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0 or 15.1.1.0.0 install rather than moving to a new public WebLogic version. The per-release patch numbers (usually a WebLogic Stack Patch Bundle or a one-off patch installed with OPatch) are listed only in CPU450, which requires a support login. That is why no public source names a fixed build or patch number.

Practical notes

  • Work from CPU450, not the CVE ID. Oracle directs customers to the Patch Availability Document for both the patch list and installation steps. The bundle for your release line will also include the other WebLogic Core fixes in this CSPU.
  • This is the monthly CSPU track, not a quarterly CPU. The quarterly October 2026 CPU fixed other WebLogic Core bugs (for example CVE-2026-91323), but this CVE is new in November. Being current with October does not cover it.
  • Verify installation on every Oracle Home. With no public fixed version string, confirm with OPatch that the patch IDs listed for your release in CPU450 are present on every WebLogic Oracle Home, including all managed server hosts, not just the Admin Server:
opatch lsinventory
  • Treat Oracle as the authority, not NVD. NVD lagged behind the vendor advisory for this CVE.

Interim exposure reduction

Oracle's advisory states that blocking the network protocols required for an attack may reduce risk until patches are applied. For this CVE, the protocol Oracle identifies is SOAP. Oracle also cautions that protocol restrictions can break application functionality, should be tested on systems outside production, and are not a long-term solution because they do not correct the underlying defect. Deployments that legitimately depend on SOAP services should take that caveat seriously. The public sources do not provide a CVE-specific firewall signature, WAF rule or configuration command.

Oracle's general guidance about removing unnecessary privileges does not apply here, since this CVE requires no privileges. Installations on unsupported releases should be moved to a supported release, because Oracle does not provide fixes for unsupported versions.

Affected systems and versions

  • Product: Oracle WebLogic Server (Oracle Fusion Middleware)
  • Component: Core
  • Explicitly affected supported releases: 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0 and 15.1.1.0.0
  • Attack prerequisite: network access to the server via SOAP, with no authentication and no user interaction

These are affected release identifiers, not fixed versions. Oracle's description covers supported versions only. The advisory does not state the status of unsupported releases, and Oracle does not ship fixes for them. Oracle documents WebLogic deployments on physical machines, virtual machines and Kubernetes clusters, so inventory work should cover all of those environments. The data sheet's statement that WebLogic underpins other Oracle products establishes deployment breadth, but does not establish that every associated Oracle service is affected by this CVE.

Vendor security history

Oracle operates three security response channels, per its Security Fixing Policies:

  • Critical Patch Update (CPU): the primary mechanism for backporting security fixes to on-premises products, released quarterly on the third Tuesday of January, April, July and October.
  • Critical Security Patch Update (CSPU): targeted fixes for critical issues in the intervening months, introduced beginning June 2026. CVE-2026-91456 shipped through this channel.
  • Security Alert: out-of-schedule patches or workarounds for particularly urgent threats.

WebLogic has a documented history of exploitation:

  • On 1 November 2020, Oracle issued a Security Alert for CVE-2020-14750, an unauthenticated WebLogic remote code execution flaw related to CVE-2020-14882, explicitly citing published exploit code. CISA urged administrators to apply the updates, and Singapore's Cyber Security Agency reported active exploitation on 3 November 2020.
  • On 1 June 2026, CISA added a separate WebLogic flaw, CVE-2024-21182, to its Known Exploited Vulnerabilities catalog based on evidence of active exploitation.

These cases show recurring attacker interest in WebLogic and an established vendor response process. They do not establish shared exploit mechanics, actor attribution or active exploitation of CVE-2026-91456. Oracle also markets WebLogic as the "#1 Java application server". That is a vendor claim rather than an independently verified market share figure.

References

Detect & fix
what others miss

Works with
  • GitHub
  • GitLab
  • Bitbucket
  • Azure DevOps Services
  • Gerrit
  • CVS
  • Jira
  • Linear
  • Slack
  • Security Compass
Explore integrations
Security magnifying glass visualization