Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify exposed WebLogic T3/IIOP listener
-
DeliveryCraft protocol-level exploit payload
-
ExploitSatisfy high-complexity attack condition
-
ExecutionTrigger Core component vulnerability
-
PersistExecute arbitrary code as WebLogic process
-
ImpactFull server takeover
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires network access to Oracle WebLogic Server's T3 or IIOP listener, both of which are enabled by default in standard WebLogic installations - no non-default configuration is required to be exposed. No authentication is required (PR:N per CVSS). High attack complexity (AC:H) means a specific condition must be satisfied during the attack, such as a timing window, race condition, or protocol state dependency, preventing trivial or fully automated exploitation by unskilled attackers. Limiting factors include: AC:H constraining reliable exploit development; network segmentation or firewall rules blocking T3 (default ports 7001/7002) and IIOP from untrusted networks; and the absence of known public exploit code at time of analysis. A tag discrepancy ('Information Disclosure' vs. full-takeover CVSS impact) has not been resolved from available data - defenders should verify precise impact scope with Oracle's advisory before finalizing risk tier decisions. |
| Impact | The CVSS 3.1 score of 8.1 conveys high intrinsic severity - full triad impact (C:H/I:H/A:H) with no authentication or user interaction required - but is tempered by AC:H, indicating that exploitation is not straightforward and likely requires meeting specific timing, state, or environmental conditions. No EPSS score was provided, no CISA KEV listing is present, and no POC code has been reported, all of which suggest this is not currently being exploited at scale. These signals together place this vulnerability in the 'high priority for patching but not emergency zero-day response' tier. One notable discrepancy: the input tags classify this as 'Information Disclosure,' yet the CVSS vector asserts full C:H/I:H/A:H impact - this conflict should be resolved by consulting Oracle's official advisory before communicating impact scope to stakeholders. T3 and IIOP ports are frequently exposed within enterprise internal networks, meaning network segmentation alone may not be a reliable compensating control in many environments. |
| Exploit ScenarioDerived | An unauthenticated remote attacker with access to WebLogic's T3 or IIOP port sends a specially crafted protocol-level request engineered to satisfy the high-complexity exploitation condition - likely a specific race condition, object state, or protocol handshake sequence. Upon meeting that condition, the attacker achieves arbitrary code execution running under the WebLogic server process account, gaining full control of the server. No public exploit code has been identified at time of analysis, but the T3/IIOP attack surface in WebLogic has produced multiple weaponized critical exploits historically, suggesting skilled actors could develop working exploit code. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 18, 2026
Full server takeover in Oracle WebLogic Server Core component is achievable by unauthenticated remote attackers via the T3 and IIOP protocols, affecting versions 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, and 15.1.1.0.0. Successful exploitation yields complete compromise of confidentiality, integrity, and availability of the targeted server instance. No public exploit has been identified at time of analysis, and exploitation is constrained by high attack complexity; however, WebLogic's T3/IIOP surface has a well-established history of critical deserialization exploits that warrants prioritized patching.
RemediationAI
Apply Oracle's Critical Patch Update for August 2026 immediately; the advisory and patch matrix are available at https://www.oracle.com/security-alerts/cspuaug2026.html. Exact patched version identifiers are not independently confirmed from the available data - the Oracle CPU advisory must be consulted to identify the correct patch for each affected release line (12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, 15.1.1.0.0). As a compensating control while patching, restrict access to WebLogic's T3 and IIOP listener ports (typically 7001, 7002 for T3; IIOP port varies by configuration) at the network perimeter to only explicitly trusted IP ranges. WebLogic's built-in Connection Filter can be configured via the administration console to block T3 from untrusted sources; note this may disrupt application functionality if T3 is used for inter-component messaging. Disabling IIOP entirely is an option if the application does not use CORBA or RMI-IIOP, but may break EJB remote access in some deployments. Do not expose T3 or IIOP to untrusted networks under any circumstances.
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 Oracle's Java EE application server widely deployed in enterprise middleware stacks. The vulnerability resides in the Core component and is exploitable specifically via T3 - WebLogic's proprietary Java object serialization protocol used for intra-cluster and client-server communication - and IIOP (Internet Inter-ORB Protocol), the CORBA/RMI transport layer. Both protocols are enabled by default and have historically served as the primary attack surface for critical deserialization and protocol-level vulnerabilities in WebLogic (e.g., CVE-2019-2725, CVE-2020-14882). No CWE identifier is provided in the available data, leaving the precise root cause class (deserialization, protocol parsing flaw, etc.) unconfirmed. Affected versions span three major release lines: 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, and 15.1.1.0.0, per Oracle's August 2026 CPU. No CPE strings were included in the source data.
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:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Network-accessible T3/IIOP with no authentication, but high complexity condition required; full triad impact consistent with server takeover as described by Oracle.
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. Difficult to exploit 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 8.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H).
Executive ViewAI
Oracle WebLogic Server versions 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, and 15.1.1.0.0 contain a critical vulnerability enabling complete server takeover by unauthenticated remote attackers via T3 and IIOP protocols. While no public exploit has been identified at this time, the attack surface has a documented history of critical deserialization exploits. Any organization running these versions faces immediate risk of full infrastructure compromise, as no vendor-released patch has been identified at time of analysis.
Restrict network access to T3 (port 7001) and IIOP (port 7002) protocols using firewalls, network segmentation, or virtual private networks; disable unnecessary remote protocols if business requirements permit; implement strict ingress/egress filtering at the perimeter; deploy intrusion detection systems (IDS) configured to alert on T3/IIOP protocol anomalies; restrict administrative console access to isolated, secure networks only; enforce multi-factor authentication on any network access to WebLogic infrastructure; and implement JVM-level monitoring for suspicious object deserialization patterns.
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
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
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-61388
GHSA-pqc7-w39c-x36g
NVD
CVE.org
EPSS
Exploit-DB