Automated Threat Modeling

Brief Summary: Oracle WebLogic Server CVE-2026-91583, Unauthenticated HTTP Takeover via TopLink Integration

A brief summary of CVE-2026-91583, a CVSS 9.8 flaw in the TopLink Integration component of Oracle WebLogic Server that allows unauthenticated takeover over HTTP. We cover the disclosed attack conditions, the affected release lines and the patch information from Oracle's November 2026 CSPU.

CVE Analysis

7 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-17

Brief Summary: Oracle WebLogic Server CVE-2026-91583, Unauthenticated HTTP Takeover via TopLink Integration

Introduction

Oracle's November 2026 Critical Security Patch Update fixes a flaw in WebLogic Server's TopLink Integration component. An unauthenticated attacker can reach it over HTTP and use it to take over the server. WebLogic hosts enterprise Java applications across on-premises, Kubernetes and cloud deployments, and the published vector requires no privileges and no user interaction. For any organization running one of the four affected release lines, CVE-2026-91583 belongs near the top of the patch queue.

This post is a brief summary of what is publicly known as of 18 November 2026. Oracle has disclosed very little about the root cause, so below we separate what the advisory establishes from what remains unresolved.

Technical information

What the disclosure establishes

The affected product is Oracle WebLogic Server, part of Oracle Fusion Middleware, and the named component is TopLink Integration. The CVE record states that the vulnerability is easily exploitable, that an unauthenticated attacker with network access via HTTP can compromise the server, and that successful attacks can result in takeover of Oracle WebLogic Server.

Oracle, acting as the CNA, assigns a CVSS 3.1 base score of 9.8. NVD publishes the same vector but has not supplied its own independent assessment.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • AV:N (Network): reachable remotely over HTTP
  • AC:L (Low): no special conditions are described as required
  • PR:N (None): no attacker authentication
  • UI:N (None): no victim interaction
  • S:U (Unchanged): impact stays within the vulnerable component's authority
  • C:H / I:H / A:H: high impact to confidentiality, integrity and availability

Per the FIRST CVSS v3.1 specification, these are Base metrics. They describe intrinsic severity and attack conditions. They do not measure the likelihood of exploitation or record an observed intrusion.

Root cause: what is known and what is not

The supplied CVE data listed no CWE. NVD now lists CWE-306, Missing Authentication for Critical Function, attributed to CISA ADP enrichment. VulDB instead assigns CWE-20 (Improper Input Validation). Neither classification should be confused with a publicly demonstrated root cause.

Oracle follows its usual disclosure policy and does not describe the defect at code level. The advisory does not identify:

  • the TopLink or EclipseLink integration class involved
  • the HTTP path, endpoint or request parameters
  • the payload format, or whether a deserialization or other handling path is involved
  • any configuration prerequisite

WebLogic is closed source, so there is no public commit or diff to inspect. Any specific claim about the vulnerable code path is speculation, and we include no code or request samples because no public source provides any.

The sources disagree on one metric. Our briefing found that Oracle's verbose (text form) risk matrix writes PR:L in the vector while still describing an unauthenticated attacker. The CVE record, NVD and the advisory's risk matrix as summarized in the patch information all publish PR:N. We follow PR:N and do not treat authentication as a protective prerequisite.

Attack flow as disclosed

Based strictly on the published conditions, the attack sequence looks like this:

  1. The attacker identifies a WebLogic Server instance running one of the affected releases and reachable over HTTP.
  2. The attacker sends HTTP traffic that reaches functionality in WebLogic's TopLink Integration layer. No credentials are needed (PR:N), and no user has to take any action (UI:N).
  3. Per AC:L, no special timing, race condition or target-specific preparation is described as necessary.
  4. Successful exploitation results in takeover of the WebLogic Server, with high impact to confidentiality, integrity and availability.

The combination of unauthenticated HTTP reachability and takeover impact matters more than the numeric score alone. The disclosure does not provide a reproducible exploit. The endpoint, payload and execution mechanics remain undisclosed.

Exploitation status

Active exploitation is not confirmed in the reviewed reporting:

  • SecurityOnline reports no confirmed exploitation.
  • A separate target-specific review, last reviewed 17 November 2026, found no exploitation reports and no public exploit, but states that community and X sources were not searched.
  • No threat actor attribution is available.
  • Rapid7 marks its CISA KEV field as False. That is a secondary database field, not direct confirmation from the CISA catalog.
  • No EPSS value was displayed on the reviewed target page.

Oracle also states that it does not distribute exploit or proof-of-concept code for its products. The absence of exploit details in the advisory therefore says nothing about whether exploits exist elsewhere, and limited visibility is not evidence of safety.

Patch information

Oracle fixed CVE-2026-91583 in its November 2026 Critical Security Patch Update (CSPU), published on 17 November 2026 as Rev 1. The Oracle WebLogic Server risk matrix lists the CVE against the TopLink Integration component, rated CVSS 3.1 9.8, reachable over HTTP with no authentication. The Notes column for this row is empty, so Oracle gives no special conditions or exceptions for the fix. The text-form risk matrix for the same release contains the matching entry.

Fixed release lines

The November 2026 patch fixes every supported release line that Oracle lists as affected:

  • 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 publishes the fix as binary patches through My Oracle Support. The advisory points Fusion Middleware customers to the patch availability document My Oracle Support Doc ID CPU450, which maps each WebLogic release (12.2.1.4, 14.1.1, 14.1.2, 15.1.1) to its specific patch or bundle number. Oracle's Fusion Middleware section also references support document KA1182. A support login is required, and the public advisory does not list a numbered fixed version.

This explains why some third-party CVE trackers show the CVE as having no fix or an unconfirmed fix, and why SecurityOnline states that no patched version is published. The vendor fix exists. A public version string and a support-distributed patch are different pieces of information, and Oracle has provided only the second.

Why a CSPU and not a quarterly CPU

Oracle now releases security patches monthly. CSPUs are intended for targeted, high-priority fixes in what Oracle calls a smaller, more focused format that is easier to apply with less disruption. They complement the quarterly cumulative Critical Patch Updates rather than replacing them.

In practice, the November CSPU patch closes this TopLink Integration flaw now, and there is no need to wait for the next quarterly CPU, which Oracle lists for 19 January 2027. The fix will be rolled into later cumulative CPU bundles. Teams that only apply quarterly patches will receive it with the next CPU, but that leaves roughly two months of exposure for a 9.8 unauthenticated issue.

Oracle tries to make Critical Patch Updates cumulative but documents exceptions that require individual patches, so teams that skipped earlier security patches should review previous advisories as well.

What the patch tells you, and what it does not

The advisory establishes that the vulnerable code sits in WebLogic's TopLink Integration layer, that it is reachable over HTTP before authentication, and that installing the November 2026 patch from Doc ID CPU450 for your release line removes the vulnerable behavior. It does not describe the changed class, endpoint or handling path.

Verifying installation

Run the following against the WebLogic ORACLE_HOME:

opatch lsinventory

Compare the installed patch IDs with the patch numbers that Doc ID CPU450 lists for your release. Repeat this on every node in the domain, including the Administration Server and all Managed Servers, because each ORACLE_HOME is patched separately.

Interim risk reduction

Where the patch cannot be applied immediately, Oracle's advisory notes that blocking network protocols required by an attack may reduce risk. For this CVE, that protocol is HTTP. SecurityOnline separately recommends restricting the affected service or interface to trusted networks, which is secondary guidance rather than an Oracle procedure for a specific TopLink endpoint. Oracle cautions that such restrictions can break application functionality, should be tested on nonproduction systems first, and are not long-term solutions because they do not correct the underlying problem.

Affected systems and versions

Oracle lists the following supported versions of Oracle WebLogic Server (Oracle Fusion Middleware, component TopLink Integration) as affected:

  • 12.2.1.4.0
  • 14.1.1.0.0
  • 14.1.2.0.0
  • 15.1.1.0.0

Per the disclosure, the vulnerable configuration is an affected release whose HTTP interface is reachable by the attacker. No authentication or user interaction is required, and the advisory states no additional configuration prerequisites.

A few scoping notes:

  • The CVE identifies product versions, not deployment models. Oracle documents WebLogic on Kubernetes, OCI and Microsoft Azure, but nothing in the disclosure exempts cloud or containerized installations of an affected release.
  • Oracle's description refers to supported affected versions. Oracle limits CSPU patches to releases under Premier Support or Extended Support and does not provide fixes for unsupported versions, so installations outside support will not receive this patch.

Vendor security history

WebLogic has prior history with this class of impact. On 3 November 2020, the Cyber Security Agency of Singapore reported active exploitation of CVE-2020-14750, a WebLogic vulnerability related to CVE-2020-14882. The advisory described unauthenticated compromise over HTTP with potential server takeover and advised immediate updates. CISA separately reported Oracle's out-of-band security alert, warning that a remote attacker could take control of an affected system.

The 2020 case is precedent only, with no bearing on attribution. CVE-2020-14750 and CVE-2026-91583 are different vulnerabilities, and the 2020 incident tells us nothing about the root cause, exploit chain or threat actors for the current issue.

Oracle runs quarterly Critical Patch Updates and, beginning June 2026, Critical Security Patch Updates in the other months, including November. Updates are available to active Oracle Support customers, and Oracle retains the ability to issue urgent patches or workaround instructions outside that schedule. The November CSPU for this CVE is an example of that monthly channel in use.

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