Service Delivery PlatformApplication · Oracle

CVE-2026-60375

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

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

dbcve analysis · high confidence

Unauthenticated remote code execution vulnerability in Oracle Fusion Middleware Service Delivery Platform's Messaging Enabler component. Exploitable via T3 and IIOP protocols, allowing complete system compromise without credentials.

MitigationApply Oracle Critical Patch Update when available; meanwhile restrict network access to T3/IIOP ports (typically 7001-7003 range) or disable the Messaging Enabler component if not required.

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

Affected products & versions

NVD · CPE data

Service Delivery PlatformApplication

Affected:all versions

CVSS breakdown

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?

dbcve checks

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

Identify Oracle Service Delivery Platform installation

Check system inventory or installed software for Oracle Service Delivery Platform. Look for Oracle middleware installation directories and the 'sdp' or 'service delivery platform' component in Oracle product listings.

Affected if Oracle Service Delivery Platform is installed on the system
Confirm Messaging Enabler component is present

Locate the Messaging Enabler component within the Oracle Fusion Middleware installation. Check for messaging-related modules in the SDP installation directory structure.

Affected if Messaging Enabler component is found in the Oracle installation
Verify T3 protocol is enabled

Examine WebLogic Server configuration files (config.xml) or the WebLogic Administration Console for T3 protocol listener settings. Check for T3 in the network channel or server configuration.

Affected if T3 protocol is enabled and configured as a network listener
Verify IIOP protocol is enabled

Examine WebLogic Server configuration for IIOP protocol settings. Check the IIOP service configuration in config.xml or through the administration console.

Affected if IIOP protocol is enabled in the WebLogic Server configuration
Check network exposure of T3/IIOP ports

Identify the listening ports for T3 (typically 7001 default) and IIOP (typically 7002 default) using netstat or similar network tools. Determine if these ports are accessible from untrusted networks.

Affected if T3 or IIOP ports are listening on network interfaces accessible from untrusted networks

If Oracle Service Delivery Platform is installed with the Messaging Enabler component and T3 or IIOP protocols are enabled and exposed to network access, the environment is vulnerable to unauthenticated remote code execution.

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

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Apply Oracle Critical Patch Update when available; meanwhile restrict network access to T3/IIOP ports (typically 7001-7003 range) or disable the Messaging Enabler component if not required.

Recommended fix Moderate confidence

Apply Oracle Critical Patch Update containing the fix for this vulnerability

1. Check Oracle's official Critical Patch Update (CPU) advisory for CVE-2026-60375 at https://www.oracle.com/security-alerts/
2. Identify the specific patch ID and download the relevant patch for your installed version (12.2.1.4.0 or 14.1.2.0.0)
3. Apply the Oracle patch following standard Oracle patching procedures for Fusion Middleware
4. Restart affected Service Delivery Platform components as instructed by the patch readme
5. Verify the patch was applied successfully and the vulnerability is resolved
6. Restrict network access to T3 and IIOP protocols if not required, using WebLogic network filters or firewall rules

Caveat Oracle patches may require downtime for application; test thoroughly in non-production environment first

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

Fix this in Service Delivery Platform Scoped from the published advisory

Consultation8.0 h
Implementation16.0 h
Testing12.0 h
Review / QA8.0 h

44.0 hours of engineering $7,720

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

www.oracle.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2026-60375?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 9.8 Critical

Exploit likelihood EPSS, next 30 days 0.5%

Affects: Service Delivery Platform

Remediation

A high-priority fix

Fix this in Service Delivery Platform 44 hrs · High

Typical engagement from $7,720

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-60375 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References