Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify exposed WebLogic T3/IIOP listener
-
DeliverySend crafted T3/IIOP request to Core
-
ExploitBypass authentication
-
ExecutionExecute arbitrary code on server
-
ImpactFull WebLogic takeover
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication mechanism validation
MITRE ATT&CK
2 techniques across 2 tactics: Defense Evasion, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the WebLogic T3 or IIOP protocol listener to be reachable from the attacker - these run on the WebLogic administration/managed-server listen port and are enabled by default, so most standard deployments are exposed unless T3/IIOP has been explicitly filtered, disabled, or firewalled. No authentication, credentials, or user interaction are needed (PR:N/UI:N), and Oracle rates it 'easily exploitable.' Affected supported versions are 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0 and 15.1.1.0.0. The primary limiting factor is network reachability of the T3/IIOP port: organizations that restrict these protocols via connection filters (weblogic.security.net.ConnectionFilterImpl) or network segmentation substantially reduce exposure. |
| Impact | This is a genuine top-priority vulnerability, and the signals largely agree. The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 9.8) is well-calibrated: Oracle's own description states an unauthenticated attacker with network access via the T3 or IIOP protocols can achieve full 'takeover' of the server, which maps cleanly to C:H/I:H/A:H with no privileges or user interaction. Oracle rates this as 'easily exploitable,' consistent with AC:L. No EPSS score, KEV listing, or public POC was provided in the input, so at time of analysis there is no public exploit identified and no confirmed active exploitation - but this must be read with caution: WebLogic T3/IIOP flaws (the Weblogic deserialization lineage, e.g. CVE-2020-2551, CVE-2020-14882) are historically among the most rapidly weaponized and mass-exploited server bugs, routinely appearing in CISA KEV and commodity botnets within weeks of a CPU. The absence of EPSS/KEV data here reflects data gaps in this feed, not low real-world risk. One labeling caveat: the CWE-287 classification and 'Authentication Bypass' tag understate the outcome - the actual impact is remote code execution/full takeover, not merely bypassing a login. Treat as critical and patch on Oracle's emergency cadence. |
| Exploit ScenarioDerived | An attacker locates an internet- or network-reachable WebLogic instance with the T3 or IIOP listener exposed (the default protocols on the WebLogic listen port) and sends a crafted T3/IIOP request that abuses the Core component to execute code without any credentials. Because no authentication or user interaction is required and the attack is network-based, this is directly exploitable at scale against exposed servers. No public POC was provided in this dataset, but this vulnerability class is historically trivial to weaponize once details or patches are diffed. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 16, 2026
Unauthenticated remote takeover of Oracle WebLogic Server is achievable through its T3 and IIOP protocol listeners in versions 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, and 15.1.1.0.0. Classified as CWE-287 (Improper Authentication) and scored CVSS 3.1 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), the flaw allows any network-reachable attacker - no credentials, no user interaction - to gain full confidentiality, integrity, and availability impact over the affected server, which Oracle itself rates 'easily exploitable'. Exploitation hinges on reachability of the T3/IIOP listeners, which are enabled by default on the WebLogic administration and managed-server listen ports, meaning most standard deployments are exposed unless those protocols are filtered, disabled, or network-segmented; no public exploit code or confirmed in-the-wild activity was identified at time of analysis, so exposure should be treated as high-impact and high-priority but not yet observed as actively exploited.
RemediationAI
Apply Oracle's fix for CVE-2026-70757 for the affected branches (12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, 15.1.1.0.0) as published in the Oracle security alert referenced by this CVE (https://www.oracle.com/security-alerts/cspusep2026.html, the cspusep2026 Critical Patch Update/Security Alert); the provided intelligence does not specify an exact patched build number, so confirm the precise patch revision against that advisory rather than assuming a version. Where immediate patching is not possible, the highest-value compensating control is to eliminate reachability of the attack path: restrict or disable the T3 and IIOP protocols using WebLogic's network connection filter (weblogic.security.net.ConnectionFilterImpl), configured via the ConnectionFilter and ConnectionFilterRules properties in the server's startup arguments or config.xml, so that only trusted management hosts can reach the listen port - the trade-off is that T3/IIOP filtering breaks remote WLST, remote EJB/JMS clients, JMX-over-T3 administration, Node Manager-style remote operations, and can disrupt cluster replication if internal server addresses are not explicitly allow-listed, so rules must whitelist the cluster members before enforcement. Network segmentation and firewall rules limiting the WebLogic listen ports to trusted management VLANs provide defense in depth with the same functional trade-offs, and disabling the T3/IIOP services outright (where the deployment relies purely on HTTP(S) servlets and no CORBA/EJB remoting) removes the vector entirely at the cost of any dependent clients. Additionally, enforce least-privilege JVM and OS service accounts so that post-compromise escalation into the host is constrained, and monitor WebLogic logs and network telemetry for anomalous T3/IIOP handshakes from unexpected source addresses as a detection measure rather than a preventive one.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Oracle WebLogic Server is a Java EE application server whose 'Core' component exposes two proprietary remote protocol endpoints in addition to standard HTTP(S): T3, Oracle's Java-serialization-based multiplexing protocol used for RMI/JNDI lookups, remote EJB, JMS, WLST and inter-server cluster traffic, and IIOP, the CORBA-based protocol for remote object invocation. CWE-287 (Improper Authentication) indicates the root cause is a failure to correctly validate or enforce authentication on a request path reachable through these listeners, allowing an unauthenticated party to cross a trust boundary that should have required proof of identity - behavior conceptually similar in class to prior WebLogic T3/IIOP abuse chains, though this CVE's specific mechanism is not detailed in the available data. The CVSS vector supplied independently (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and the vendor's own scoring agree that no privileges or interaction are prerequisite and that the impact is scope-limited to the WebLogic component itself but total within it. Because both T3 and IIOP are bound to the same listen port as normal administration traffic (for example 7001/7002 by default) and are not disabled out of the box, the practical exposure is governed almost entirely by whether those protocols are reachable from untrusted networks; WebLogic's built-in weblogic.security.net.ConnectionFilterImpl mechanism and equivalent firewall rules are the primary architectural controls that break the attack path. The ENISA EUVD record (EUVD-2026-79512) independently enumerates the same four affected release branches, and the Oracle reference points to the cspusep2026 security alert as the authoritative advisory.
Know when Weblogic Server gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Unauthenticated network attacker over default-enabled T3/IIOP achieves full server takeover with no user interaction, yielding AV:N/AC:L/PR:N/UI:N and C:H/I:H/A:H.
Primary rating from Vendor (oracle).
CVSS VectorVendor: oracle
DescriptionCVE.org
Vulnerability in the Oracle WebLogic Server product of Oracle Fusion Middleware (component: Core). Supported versions that are affected are 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0 and 15.1.1.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via T3, IIOP to compromise Oracle WebLogic Server. Successful attacks of this vulnerability can result in takeover of Oracle WebLogic Server. CVSS 3.1 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
Executive ViewAI
Oracle WebLogic Server - a platform widely used to host revenue-critical Java applications - is affected by a critical authentication bypass (CVE-2026-70757, CVSS 9.8) that lets any attacker with network reach to the default T3/IIOP listener ports take full control of the server without credentials or user interaction. Because those listeners are enabled by default on administration and managed-server ports in versions 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, and 15.1.1.0.0, most standard deployments are exposed today, and no vendor patch is available - meaning mitigation must be architectural and network-based rather than patch-based. Leadership should treat this as a high-priority exposure-management event: business impact is currently potential rather than realized (no public exploit identified at time of analysis), but any successful exploitation would mean full loss of confidentiality, integrity, and availability for the affected systems and the data and services they support.
No vendor-released patch identified at time of analysis; interim mitigations are network and configuration based. Restrict or fully block network access to T3 and IIOP listener ports (administration and managed-server listen ports) at perimeter firewalls, security groups, and inter-segment boundaries. Where T3/IIOP are not operationally required, disable them; where they are required, enforce WebLogic connection filters (weblogic.security.net.ConnectionFilterImpl) that allow only named trusted hosts, and place affected servers behind segmented networks and reverse proxies/WAFs that reject T3 and IIOP from untrusted sources. Add logging, alerting, and egress monitoring for T3/IIOP activity, and perform compromise assessment on any instance that was exposed. Note: the vulnerability is unauthenticated per the CVSS vector (PR:N) and reachability of the T3/IIOP listeners is the determining exposure factor; no public exploit was identified at time of analysis.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Weblogic Server
View allVulnerability in the Oracle WebLogic Server component of Oracle Fusion Middleware (subcomponent: Web Services). Rated cr
The Jakarta Multipart parser in Apache Struts 2 2.3.x before 2.3.32 and 2.5.x before 2.5.10.1 has incorrect exception ha
Oracle WebLogic Server allows unauthenticated remote code execution through the WLS Security component's T3 protocol, ma
Unspecified vulnerability in the Oracle WebLogic Server component in Oracle Fusion Middleware 10.3.6.0, 12.1.3.0, and 12
Vulnerability in the Oracle WebLogic Server component of Oracle Fusion Middleware (subcomponent: Core Components). Rated
In Apache Log4j 2.x before 2.8.2, when using the TCP socket server or UDP socket server to receive serialized log events
In Spring Framework, versions 5.2.x prior to 5.2.3, versions 5.1.x prior to 5.1.13, and versions 5.0.x prior to 5.0.16,
Unspecified vulnerability in the Oracle WebLogic Server component in Oracle Fusion Middleware 10.3.6, 12.1.2, 12.1.3, an
Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) did not protect from uncontrolled recursio
JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Lo
A denial of service flaw was found in OpenSSL 0.9.8, 1.0.1, 1.0.2 through 1.0.2h, and 1.1.0 in the way the TLS/SSL proto
FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, rela
EUVD-2026-79512
GHSA-49v7-8ppc-2g98
NVD
CVE.org
EPSS
Exploit-DB