dbcve.org
Weblogic ServerApplication · Oracle

CVE-2026-60196

HIGH · 8.4 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 →
86/100
Remediation priority · High
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 and 14.1.2.0.0. Easily exploitable vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the Oracle WebLogic Server executes to compromise Oracle WebLogic Server. While the vulnerability is in Oracle WebLogic Server, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle WebLogic Server. CVSS 3.1 Base Score 8.4 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/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 · moderate confidence

A vulnerability in Oracle WebLogic Server Core component (versions 12.2.1.4.0 and 14.1.2.0.0) allows a high-privileged attacker with physical access to the network segment to compromise the server and potentially take it over, with scope change affecting additional products.

MitigationApply Oracle Critical Patch Update (CPU) patches for WebLogic Server; restrict physical and network access to the hardware; limit high-privileged account access.

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.2.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
Adjacent
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/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. Identify WebLogic Server installation and version
    Locate the WebLogic installation directory and check the version file. Common locations include: PRODUCT_HOME/oracle_common/modules/oracle.core/ version.txt, or check the registry/inventory files in the Oracle Home directory. Run: find $ORACLE_HOME -name 'version.txt' 2>/dev/null or check the inventory file.
    Affected if The installed version is 12.2.1.4.0 or 14.1.2.0.0 exactly matching the affected versions
  2. Confirm WebLogic Server is running
    Check if the WebLogic Server process is active. Common commands: ps -ef | grep -i weblogic on Linux, or check Windows services for WebLogic. Also verify the Admin Server or Managed Server ports are listening.
    Affected if WebLogic Server processes are running and the version from step 1 matches the affected versions
  3. Verify Core component is loaded
    The Core component is a default part of WebLogic Server. Check the installed modules under $ORACLE_HOME/oracle_common/modules/oracle.core/ or review the config.xml for core module references. This component ships with standard installations.
    Affected if The Core component is present in the installation, which is the default state for standard WebLogic Server deployments
  4. Assess network exposure of management interfaces
    Review network configuration to determine if management ports (default 7001 for Admin Server, 7002 for HTTPS, or configured ports) are accessible from adjacent network segments. Use netstat -an | grep LISTEN or firewall rules to identify listening interfaces and their bound addresses.
    Affected if Management interfaces are bound to accessible network interfaces and can be reached from the adjacent network segment as described in the attack vector

If the installed version exactly matches 12.2.1.4.0 or 14.1.2.0.0 AND WebLogic Server is running with exposed management interfaces, the environment is affected by this vulnerability.

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 Update (CPU) patches for WebLogic Server; restrict physical and network access to the hardware; limit high-privileged account access.

Recommended fix Moderate confidence

Apply the Oracle Critical Patch Update containing the fix for CVE-2026-60196 (check Oracle Critical Patch Update advisory for patch numbers for 12.2.1.4.0 and 14.1.2.0.0)

  1. Check Oracle's official Critical Patch Update advisory for this CVE at https://www.oracle.com/security-alerts/ to identify the specific patch number for WebLogic Server 12.2.1.4.0 and 14.1.2.0.0
  2. Apply the Oracle Critical Patch Update (CPU) that addresses CVE-2026-60196 to both affected WebLogic Server instances
  3. After patching, restart the WebLogic Server managed servers and admin server to load the fixed components
  4. Verify the patch was applied successfully by checking the WebLogic Server version and reviewing the applied patches via the Administration Console or WLST command `listPatches()`
  5. If no CPU patch is available yet, monitor Oracle's Security Alert page for upcoming patch releases
Caveat Oracle CPU patches are cumulative and typically backward-compatible; however, test in staging before production deployment to verify application functionality

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

Fix this in Weblogic Server Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-60196 — 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-60196 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