External risk intelligence

Oracle WebLogic Server SOAP Takeover Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-91456

Oracle WebLogic Server is a middleware product frequently deployed as a public-facing web server or application gateway to provide web services. The vulnerability specifically targets the SOAP interface, which is commonly exposed to the internet to facilitate remote communication and integration, making it a high-traffic, internet-facing attack surface by design.

Halo Surface Signal: 5 out of 5 — more likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability has been identified in Oracle WebLogic Server, a widely used middleware product. This issue is easily exploitable by unauthenticated attackers over the network, potentially leading to a complete takeover of the affected server. Given that WebLogic Server often handles public-facing web services and integrations, this vulnerability presents a significant risk to systems accessible from the internet.

  • Unauthenticated attackers can take over affected servers.
  • It impacts internet-facing systems using Oracle WebLogic.
  • Confirm exposure to ensure business continuity.

Attack Path

How an attacker could exploit the issue

An attacker can exploit this vulnerability by sending a crafted SOAP request over the network to an exposed Oracle WebLogic Server. This allows them to directly interact with the Core component without needing any prior authentication, ultimately leading to a complete takeover of the server.

  • Network access, no authentication needed.
  • Triggered via crafted SOAP requests.
  • Leads to full server takeover.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an unauthenticated attacker to take over an Oracle WebLogic Server when accessed via SOAP. This could lead to unauthorized control and manipulation of the server and its resources.

  • Oracle WebLogic Server.
  • Network access via SOAP.
  • Complete server takeover.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Oracle WebLogic Server component is likely managed by infrastructure, platform, or application teams, depending on the specific deployment model. The immediate practical step is to locate all instances of this technology, assess their network exposure and business criticality, identify the accountable owner for each instance, and then prioritize remediation efforts.

  • Infrastructure or platform teams own the issue.
  • Verify public-facing or critical instances first.
  • Plan coordinated remediation based on risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Oracle WebLogic Server?

Oracle WebLogic Server is a middleware platform used to build, deploy, and run enterprise-level Java applications. It acts as an application server, managing business logic, database connectivity, and web services for organizations. It is frequently deployed as a core gateway to handle communication between different software systems.

How does CVE-2026-91456 work?

This vulnerability involves a flaw in the product's Core component that fails to properly secure incoming data. It is classified as an improper input validation issue that allows an unauthenticated user to send commands to the server. Because the system does not verify the request, an attacker can leverage this path to gain unauthorized control over the server's operations.

What triggers this vulnerability?

An attacker triggers the bug by sending a specifically crafted SOAP request to the server over the network. No prior login or authentication is required for the attack to succeed. Importantly, interactions that do not utilize the SOAP protocol or requests that do not follow the specific crafted format do not initiate this particular vulnerability.

Is my server at risk if it is internal?

Halo Surface Signal indicates that while this flaw is reachable via network access, systems that are internet-facing are at the highest risk because they are reachable without restriction. While internal servers remain theoretically susceptible if an attacker gains access to your private network, public-facing instances are the primary concern due to their constant exposure to the open internet.

How do I respond to this vulnerability?

Begin by creating a comprehensive inventory of all WebLogic Server instances in your environment to understand your footprint. Coordinate with your platform and infrastructure teams to prioritize servers based on their network accessibility and business importance. Ensure you are tracking official security updates from Oracle to apply the necessary patches as soon as they become available.

References