dbcve.org
Weblogic ServerApplication · Oracle

CVE-2026-60200

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 4 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 SOAP 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).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Unauthenticated remote code execution vulnerability in Oracle WebLogic Server Core component via SOAP interface, affecting versions 12.2.1.4.0 through 15.1.1.0.0. Allows attackers with network access to completely compromise the server, achieving full confidentiality, integrity, and availability takeover.

MitigationApply Oracle critical patch updates immediately, restrict network access to SOAP endpoints, and implement a Web Application Firewall as a compensating control until patching is possible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Weblogic ServerApplication
Affected:= 12.2.1.4.0= 14.1.1.0.0= 14.1.2.0.0= 15.1.1.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm WebLogic Server installation
    Locate the WebLogic installation directory and identify the version. Common paths include $ORACLE_HOME/wlserver or C:\Oracle\Middleware\wlserver. Check for the existence of the WebLogic core JAR files (weblogic.jar) in the lib directory.
    Affected if WebLogic Server is installed on the system
  2. Check installed WebLogic version
    Run the WebLogic version command or inspect the product version file. In the installation directory, look for a version file or execute: java -jar weblogic.jar -version. Alternatively, check the console output when starting the WebLogic Server.
    Affected if The installed version matches 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, or 15.1.1.0.0 exactly
  3. Verify SOAP endpoints are enabled
    Inspect the WebLogic configuration files (config.xml) and deployment descriptors (weblogic.xml, web.xml) for SOAP web service configurations. Check for the presence of JAX-WS or JAX-RPC web service deployments in the config.xml under the <app-deployment> or <web-app> sections.
    Affected if SOAP-based web services are configured and deployed on the server
  4. Confirm SOAP endpoint network exposure
    Review the network listener configuration in the WebLogic Administration Console or config.xml. Check the <listen-address> and port settings for the managed servers or admin server hosting SOAP endpoints. Verify if these endpoints are bound to external network interfaces rather than localhost only.
    Affected if SOAP endpoints are accessible on routable network interfaces (not restricted to localhost or internal networks)

The environment is affected if WebLogic Server versions 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, or 15.1.1.0.0 are installed AND SOAP endpoints are enabled and network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle critical patch updates immediately, restrict network access to SOAP endpoints, and implement a Web Application Firewall as a compensating control until patching is possible.

Recommended fix Moderate confidence

Contact Oracle for the latest supported version; standard practice is to apply CPU patches rather than version upgrades for security fixes

  1. Apply the latest Oracle Critical Patch Update (CPU) that addresses CVE-2026-60200. Check Oracle's official CPU advisory for the specific patch bundle.
  2. Alternatively, contact Oracle Support to obtain the specific patch for this vulnerability.
  3. After applying the patch, restart the WebLogic Server to ensure the vulnerability is remediated.
  4. Verify the fix by reviewing the patch documentation and confirming the CVE is listed as addressed in the Oracle Critical Patch Update advisory.
Caveat Apply CPU patches during a scheduled maintenance window as they may require server restart

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Weblogic Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-60200 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-60200 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data