dbcve.org
Service Delivery PlatformApplication · Oracle

CVE-2026-60387

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 Service Delivery Platform product of Oracle Fusion Middleware (component: Messaging Enabler). Supported versions that are affected are 12.2.1.4.0 and 14.1.2.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via T3, IIOP to compromise Service Delivery Platform. Successful attacks of this vulnerability can result in takeover of Service Delivery Platform. 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

Critical unauthenticated remote code execution vulnerability in Oracle Fusion Middleware Service Delivery Platform's Messaging Enabler component. Attackers can exploit via T3 or IIOP network protocols without any credentials, achieving complete system takeover due to high Confidentiality, Integrity, and Availability impact.

MitigationApply Oracle Critical Patch Updates for affected versions 12.2.1.4.0 and 14.1.2.0.0; if patches unavailable, restrict network access to T3/IIOP ports or disable these protocols where not required.

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
Service Delivery PlatformApplication
Affected:all versions

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. Identify if Oracle Service Delivery Platform is installed
    Check for the presence of Oracle Service Delivery Platform installation directories or look for 'Oracle Service Delivery Platform' or 'SDP' in installed software listings on the system.
    Affected if The software is found on the system.
  2. Determine installed version
    Locate and inspect version files or use Oracle inventory commands (like 'opatch lsinventory' or Oracle inventory listings) to find the exact version number of the Oracle Service Delivery Platform installation.
    Affected if The installed version matches 12.2.1.4.0 or 14.1.2.0.0, or falls within the range of these versions, or is any version (since all versions are affected).
  3. Verify if Messaging Enabler component is present
    Check for the Messaging Enabler component within the Oracle Service Delivery Platform installation, typically found in the component or module listing of the product.
    Affected if The Messaging Enabler component is installed and enabled.
  4. Check if T3 protocol is enabled and exposed
    Inspect Oracle WebLogic Server configuration files (config.xml) or the administration console for T3 protocol listeners. Look for T3 or T3S entries in the network channel configurations.
    Affected if T3 protocol is enabled and accessible from the network.
  5. Check if IIOP protocol is enabled and exposed
    Inspect Oracle WebLogic Server configuration for IIOP protocol settings. Look for IIOP endpoints in the administration console or configuration files.
    Affected if IIOP protocol is enabled and accessible from the network.

The system is affected if Oracle Service Delivery Platform with the Messaging Enabler component is installed, any version including 12.2.1.4.0 or 14.1.2.0.0, and T3 or IIOP protocols 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Updates for affected versions 12.2.1.4.0 and 14.1.2.0.0; if patches unavailable, restrict network access to T3/IIOP ports or disable these protocols where not required.

Fix this in Service Delivery Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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