dbcve.org
Managed File TransferApplication · Oracle

CVE-2026-60545

HIGH · 8.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 →
94/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. Successful attacks of this vulnerability can result in takeover of Oracle Managed File Transfer. CVSS 3.1 Base Score 8.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/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 · moderate confidence

Vulnerability in Oracle Managed File Transfer (MFT) Runtime Server affecting versions 12.2.1.4.0 and 14.1.2.0.0 allows low-privileged attackers with network access via HTTP to achieve complete takeover of the MFT system, impacting confidentiality, integrity, and availability.

MitigationRestrict network access to MFT Runtime Server to trusted sources only; monitor for unauthorized access attempts; apply Oracle patches when available. Follow principle of least privilege for MFT user accounts.

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 Oracle MFT installation and version
    Locate the Oracle MFT installation directory and check the version.properties or version.txt file, typically found in the MFT home directory (e.g., $ORACLE_HOME/mft). Alternatively, use the Oracle OPatch lsinventory command or check the oracle.mft jar file manifest for version information.
    Affected if The installed version is exactly 12.2.1.4.0 or exactly 14.1.2.0.0
  2. Verify MFT Runtime Server is running
    Check if the MFT Runtime Server process is active. This can be done by querying the WebLogic Administration Console, checking for the MFT managed server process, or using OS-level commands like 'ps' to find the MFT Runtime Server Java process.
    Affected if The MFT Runtime Server process is running and listening on network ports (typically HTTP ports 7100-7103 or configured HTTPS ports)
  3. Confirm HTTP/HTTPS network exposure
    Examine the MFT Runtime Server configuration in the WebLogic Administration Console or check the configuration XML files (such as config.xml) to determine which network listeners and ports are enabled. Verify if HTTP (non-SSL) listeners are active.
    Affected if The MFT Runtime Server is accessible over HTTP (not restricted to localhost only) on any network interface
  4. Check for low-privileged MFT accounts
    Review the MFT user repository (via WebLogic Console or the embedded LDAP) to identify accounts with low-privileged roles that could be used for initial network access. Verify which user roles have network-facing access to MFT endpoints.
    Affected if There exist low-privileged user accounts (non-admin roles) that have network-accessible authentication to the MFT Runtime Server

You are affected if your Oracle Managed File Transfer is version 12.2.1.4.0 or 14.1.2.0.0, the MFT Runtime Server is running and exposed over HTTP/HTTPS on a network interface, and an attacker with network access could authenticate with a low-privileged account.

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

Restrict network access to MFT Runtime Server to trusted sources only; monitor for unauthorized access attempts; apply Oracle patches when available. Follow principle of least privilege for MFT user accounts.

Fix this in Managed File Transfer Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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