dbcve.org
Data IntegratorApplication · Oracle

CVE-2026-60999

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 Data Integrator product of Oracle Fusion Middleware (component: Rest Service). The supported version that is affected is 14.1.2.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTPS to compromise Oracle Data Integrator. Successful attacks of this vulnerability can result in takeover of Oracle Data Integrator. 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

A critical vulnerability in Oracle Data Integrator's REST Service component allows unauthenticated remote attackers to achieve complete system compromise via network requests. The flaw is easily exploitable and affects version 14.1.2.0.0, enabling full takeover of confidentiality, integrity, and availability.

MitigationApply the Oracle Critical Patch Update for Oracle Data Integrator version 14.1.2.0.0. If no patch is available, restrict network access to the REST Service endpoint via firewall or web application firewall until a patch is released.

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
Data IntegratorApplication
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
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. Verify Oracle Data Integrator installation
    Locate ODI installation directory or check for ODI processes running on the system. Common locations include $ORACLE_HOME/odi or check for 'odi' or 'oracledi' directories. In Windows, check Program Files for Oracle Data Integrator.
    Affected if Oracle Data Integrator software is present on the system
  2. Confirm ODI version number
    Check the installed ODI version. This can typically be found in: the installation logs, the about screen in ODI Studio (ODIS), or by querying the ODI repository. Look for a version property file or use ODI Studio help > about. Compare the version to 14.1.2.0.0.
    Affected if The installed version is exactly 14.1.2.0.0
  3. Determine if REST Service is configured
    Check for REST Service configuration in the ODI deployment. Look for REST-related configuration files in the ODI domain configuration, or check if a REST endpoint is accessible. Common paths include: $DOMAIN_HOME/config/fmwconfig/components/ODI/ or check for rest endpoints in the ODI Enterprise Manager.
    Affected if The ODI REST Service component is deployed and accessible
  4. Verify network accessibility of REST endpoints
    Attempt to reach the ODI REST endpoints from a network perspective. Common endpoints follow patterns like /odi/di/v1/ or check if port 7001/7002 (typical WebLogic ports) responds to REST calls. Use curl or a browser to test HTTPS access to known REST paths.
    Affected if The REST Service is reachable over HTTPS from the network

If Oracle Data Integrator version 14.1.2.0.0 is installed with the REST Service enabled and network-accessible, the environment is vulnerable to unauthenticated remote code execution.

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 the Oracle Critical Patch Update for Oracle Data Integrator version 14.1.2.0.0. If no patch is available, restrict network access to the REST Service endpoint via firewall or web application firewall until a patch is released.

Fix this in Data Integrator 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-60999 — 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-60999 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