Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-60696 – Unauthenticated Remote Code Execution – Oracle WebLogic Server (12.2.1.4.0–15.1.1.0

Be the first to know when new zero-days emerge:

Summary

CVE-2026-60696 is a critical vulnerability in the Core component of Oracle WebLogic Server (part of Oracle Fusion Middleware) that allows a remote, unauthenticated attacker to fully compromise the server. Oracle rates it as easily exploitable over the network via the T3 or IIOP protocols, with no privileges or user interaction required. Successful exploitation results in complete takeover of the affected WebLogic Server instance.

Technical details

  • Root cause: A flaw in the WebLogic Server Core component that can be triggered through the server’s own protocol handlers rather than through the HTTP web tier.
  • Trigger conditions: An attacker only needs network access to the WebLogic Server’s T3 or IIOP listener ports; no authentication or user interaction is needed.
  • Attack vector: Network-based (AV:N), low attack complexity (AC:L), delivered via the T3 or IIOP protocols used for WebLogic’s RMI/EJB communication.
  • Impact: Full compromise of confidentiality, integrity, and availability — described by Oracle as resulting in takeover of the WebLogic Server.

Affected software

  • Oracle WebLogic Server 12.2.1.4.0
  • Oracle WebLogic Server 14.1.1.0.0
  • Oracle WebLogic Server 14.1.2.0.0
  • Oracle WebLogic Server 15.1.1.0.0

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Apply the patch for CVE-2026-60696 issued in Oracle’s August 2026 Critical Patch Update (Security Alert), updating affected WebLogic Server 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, and 15.1.1.0.0 installations to the fixed release Oracle provides for this advisory.
  • If immediate patching is not possible: Restrict network access to the T3 and IIOP protocols/ports so they are not reachable from untrusted networks or the public internet, and disable these protocols on WebLogic channels where they are not required, until patching can be completed.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Response header Set-Cookie: WebLogicSession=
  • Response header Server: WebLogic, WebLogic server

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge