Managed File TransferApplication · Oracle

CVE-2026-60549

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

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

dbcve analysis · high confidence

Vulnerability in Oracle Managed File Transfer's MFT Runtime Server allows low privileged attackers with network access via HTTP to achieve complete system takeover. The flaw affects versions 12.2.1.4.0 and 14.1.2.0.0 with CVSS 3.1 score of 8.8, indicating high impact across confidentiality, integrity, and availability.

MitigationApply the appropriate Oracle Critical Patch Update for Oracle Managed File Transfer. Until patched, restrict network access to MFT Runtime Server endpoints and monitor for suspicious HTTP activity.

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

Managed File TransferApplication

Affected:= 12.2.1.4.0= 14.1.2.0.0

CVSS breakdown

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?

dbcve checks

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

Verify Oracle MFT is installed

Locate the Oracle MFT installation directory, typically under $ORACLE_HOME/mft or check for the presence of MFT-specific directories and executables in the Oracle Fusion Middleware home structure.

Affected if Oracle Managed File Transfer software is not present on the system.
Check MFT Runtime Server version

Use the Oracle Opatch utility (opatch lspatches) or check the MFT inventory file to identify the exact version of the MFT Runtime Server component installed.

Affected if The installed version matches exactly 12.2.1.4.0 or 14.1.2.0.0.
Confirm MFT Runtime Server is running

Check if the MFT Runtime Server process is active by querying the WebLogic Server administration console, using WLST, or checking for Java processes running the MFT runtime component.

Affected if The MFT Runtime Server process is actively running and listening on network ports.
Verify network accessibility of MFT Runtime Server

Identify the HTTP/HTTPS listener ports configured for MFT (typically through WebLogic Server console or config.xml) and confirm they are reachable from the network using tools like netstat or nmap.

Affected if The MFT Runtime Server HTTP endpoint is exposed to the network and accessible remotely.
Assess authentication configuration

Review the WebLogic security realm configuration and MFT-specific user roles to determine if low-privileged users can access the MFT runtime interface.

Affected if Low-privileged or standard MFT users can authenticate to the MFT Runtime Server interface.

The environment is affected if Oracle MFT Runtime Server is installed and running with version 12.2.1.4.0 or 14.1.2.0.0, and the HTTP interface is network-accessible to authenticated users.

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 the appropriate Oracle Critical Patch Update for Oracle Managed File Transfer. Until patched, restrict network access to MFT Runtime Server endpoints and monitor for suspicious HTTP activity.

Recommended fix Moderate confidence

Upgrade to the latest Oracle Managed File Transfer version (14.1.2.x or later) as specified in the corresponding Critical Patch Update. Check Oracle's CPU advisory for the exact patched version number.

1. Review Oracle's official Critical Patch Update (CPU) advisory for the quarter containing this CVE at https://www.oracle.com/security-alerts/
2. Identify the specific patch ID and download link for Oracle Managed File Transfer version 12.2.1.4.0 or 14.1.2.0.0
3. Download the appropriate patch from Oracle Support (support.oracle.com) using your Oracle Support credentials
4. Apply the patch following Oracle's standard MFT patching documentation, typically involving:
a. Stop the MFT Runtime Server and MFT Admin Server services
b. Backup the existing Oracle Middleware home directory
c. Execute the patch installer with appropriate privileges
d. Verify the patch was applied successfully

Caveat Review Oracle's patch readme for any known issues or required post-patch configuration changes. Some patches may require additional steps or have specific compatibility considerations.

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

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-60549 — 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-60549 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-60549?

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 8.8 High

Exploit likelihood EPSS, next 30 days 0.4%

Affects: Managed File Transfer

Remediation

A high-priority fix

Fix this in Managed File Transfer 30 hrs · Moderate

Typical engagement from $5,280

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-60549 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