dbcve.org
Managed File TransferApplication · Oracle

CVE-2026-60537

CRITICAL · 9.9 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 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 Managed File Transfer product of Oracle Fusion Middleware (component: MFT Runtime Server). Supported versions that are affected are 12.2.1.4.0 and 14.1.2.0.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Managed File Transfer. While the vulnerability is in Oracle Managed File Transfer, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle Managed File Transfer. CVSS 3.1 Base Score 9.9 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/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

Critical vulnerability in Oracle Managed File Transfer (MFT) Runtime Server allowing low-privileged attackers with network access via HTTP to achieve complete takeover of the MFT server. The CVSS vector indicates exploitation requires no user interaction, uses network attack vector, and achieves changed scope impact with complete confidentiality, integrity, and availability compromise.

MitigationApply the applicable Oracle Critical Patch Update (CPU) or security patch for Oracle Managed File Transfer versions 12.2.1.4.0 and 14.1.2.0.0. If immediate patching is not feasible, restrict network access to MFT Runtime Server endpoints and implement additional authentication controls.

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
Managed File TransferApplication
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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 Oracle MFT installation
    Search for Oracle Managed File Transfer installation directories (commonly under $ORACLE_HOME/mft or /u01/oracle/mft) and check for mft.jar or mft.ear files. On Linux, run: find / -name '*mft*' -type f 2>/dev/null | head -20
    Affected if Oracle Managed File Transfer software is found on the system
  2. Verify MFT version
    Check the version of the installed MFT. Look for a version file in the MFT installation directory, or query the MFT Runtime Server admin interface if accessible. Check for manifest files: find <mft_install_dir> -name 'MANIFEST.MF' -o -name 'version.txt' 2>/dev/null
    Affected if Installed version matches 12.2.1.4.0 or 14.1.2.0.0 exactly
  3. Confirm MFT Runtime Server is running and exposed
    Check if the MFT Runtime Server process is active. On Linux: ps -ef | grep -i mft. Identify the HTTP listener port (typically 8080, 8001, or 8888 for MFT). Verify with: netstat -tlnp | grep -E '(8080|8001|8888)' or ss -tlnp
    Affected if MFT Runtime Server process is running and listening on a network port accessible via HTTP
  4. Assess network exposure
    Review firewall rules and network configuration to determine if the MFT HTTP port is accessible from untrusted networks. Check iptables, host firewall, or cloud security groups. Run: iptables -L -n or systemctl status firewalld
    Affected if MFT Runtime Server HTTP port is open to untrusted/network-accessible hosts

The environment is affected if Oracle Managed File Transfer version 12.2.1.4.0 or 14.1.2.0.0 is installed with MFT Runtime Server running and exposed to network access.

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 applicable Oracle Critical Patch Update (CPU) or security patch for Oracle Managed File Transfer versions 12.2.1.4.0 and 14.1.2.0.0. If immediate patching is not feasible, restrict network access to MFT Runtime Server endpoints and implement additional authentication controls.

Fix this in Managed File Transfer Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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