Automated Threat Modeling

Overview of CVE-2026-114827: Authenticated Takeover Flaw in the Oracle Managed File Transfer MFT Runtime Server

A brief summary of CVE-2026-114827, a CVSS 8.8 flaw in the Oracle Managed File Transfer MFT Runtime Server that lets a low-privileged user with HTTP access take over the product. Includes patch information from Oracle's November 2026 Critical Security Patch Update.

CVE Analysis

7 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-17

Overview of CVE-2026-114827: Authenticated Takeover Flaw in the Oracle Managed File Transfer MFT Runtime Server

Introduction

Oracle's November 2026 Critical Security Patch Update includes a fix for a flaw in the Oracle Managed File Transfer (MFT) Runtime Server that allows an authenticated, low-privileged user with HTTP access to take over the product. Oracle rates the issue CVSS 3.1 8.8 with high confidentiality, integrity and availability impact, and describes it as easily exploitable. That makes it relevant for any organization running MFT as the file exchange point between internal systems and external partners.

Oracle Managed File Transfer is a component of Oracle Fusion Middleware that Oracle positions for exchanging and managing files between internal departments and external partners, with reporting, audit trails, encryption, scheduling, and embedded FTP and Secure FTP servers. An independent market report names Oracle among participants in the managed file transfer market, although the material we reviewed does not establish a specific market share. MFT integrates with WebLogic identity management, SOA Suite, and B2B, so it usually sits inside a broader Oracle middleware estate rather than as a standalone tool.

Technical information

What Oracle has disclosed

Oracle's description is short. The vulnerability is in the MFT Runtime Server component of Oracle Managed File Transfer, it is easily exploitable, and it allows a low-privileged attacker with network access via HTTP to compromise the product. Successful attacks can result in takeover of Oracle Managed File Transfer.

The full CVSS 3.1 vector is:

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Broken down:

  • Attack vector: Network (HTTP)
  • Attack complexity: Low
  • Privileges required: Low
  • User interaction: None
  • Scope: Unchanged
  • Confidentiality / Integrity / Availability: High / High / High
  • Base score: 8.8

Oracle's risk matrix marks this CVE as not remotely exploitable without authentication. The attack needs an account, but only a low-privileged one, not an administrative one.

Root cause: what is and is not known

Oracle MFT is closed source, so there is no public commit, diff, or code snippet showing what changed in the MFT Runtime Server. The official CVE record and OpenCVE list no CWE. VulDB separately classifies the issue as CWE-269 (Improper Privilege Management), while describing the affected code and input as unknown. We treat that as a secondary database classification, not as a vendor-published explanation of the defect.

The public material does not identify a vulnerable URL, request parameter, payload format, affected function, or detailed exploitation sequence. The stated impact is product takeover. The description does not specify an operating system command execution mechanism, and we do not infer one.

Attack flow supported by the public data

Based only on Oracle's description and vector, the attack conditions look like this:

  1. The attacker holds a low-privileged account that the MFT deployment accepts (PR:L).
  2. The attacker has network reachability to the MFT Runtime Server over HTTP (AV:N).
  3. The attacker sends requests to the Runtime Server. No victim interaction is needed (UI:N), and Oracle rates the complexity as low (AC:L). The specific requests are not public.
  4. The result is takeover of Oracle Managed File Transfer, with high impact on confidentiality, integrity and availability within the product's own security scope (S:U).

Anything more granular than this, such as a request sequence or endpoint, would be speculation.

Exploitation status

VulDB reports that neither technical details nor an exploit are publicly available and lists no active actors or APT groups for this entry. We found no CVE-specific campaign, ransomware use, or indicators in the reviewed sources. The CVE was absent from the retrieved CISA Known Exploited Vulnerabilities snapshot (version 2026.11.17, released at 17:53:15.5664 UTC on November 17, 2026), but that snapshot predates the CVE record publication at 21:31:23.960 UTC the same day, so the absence tells us nothing about current catalog status. Oracle's advisory includes a general warning about attempts to exploit vulnerabilities that already have patches. That warning covers Oracle's whole portfolio and is not evidence that this CVE is being exploited.

Publication timeline

  • The official CVE record was published on November 17, 2026 at 21:31:23.960 UTC, with Oracle as the assigning organization.
  • Oracle's advisory lists November 17, 2026 as its initial release date.
  • The supplied NVD timestamp (November 17, 2026 at 22:18:10.743) could not be independently confirmed. The NVD page returned "CVE ID Not Found" when retrieved, and the NVD record was later reported in the "Received" state.

Patch information

Oracle released a vendor fix for CVE-2026-114827 in its Critical Security Patch Update (CSPU) for November 2026, published November 17, 2026. All patch information comes from Oracle's advisory, its text-form risk matrix, and its CSAF record.

How the fix is delivered

The fix ships in a CSPU rather than in the regular quarterly Critical Patch Update (CPU). Oracle describes a CSPU as a smaller, more focused set of high-priority security fixes. CSPUs add to the cumulative quarterly CPUs rather than replacing them. The October 2026 CPU already contained separate MFT Runtime Server fixes (for example, CVEs related to Apache Mina), so applying the October CPU does not fix CVE-2026-114827. The November CSPU must be applied on top of it.

In the November CSPU, Oracle Fusion Middleware received 71 new security patches, including this one. The Oracle Managed File Transfer risk matrix entry reads:

  • Component: MFT Runtime Server
  • Protocol: HTTP
  • Remote exploit without auth: No
  • CVSS 3.1: 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H)
  • Supported versions patched: 12.2.1.4.0, 14.1.2.0.0
  • Footnotes: None

What the CSAF record says

Oracle's CSAF advisory (cspunov2026csaf.json) contains a remediation entry for this CVE with:

  • Category: vendor_fix, meaning a code fix rather than only a workaround
  • Products covered: both the 12.2.1.4.0 and 14.1.2.0.0 release lines
  • Details: fixes are available to "Oracle customers with valid support contracts"
  • Reference: My Oracle Support patch availability document CPU450

CPU450 is the Fusion Middleware patch availability document. It maps each affected product version to the specific patch numbers to download, so administrators go there to find the MFT patch for their release.

Verifying the fix

Oracle has not published a separate "fixed in" version string. The fix is applied as a patch to an existing 12.2.1.4.0 or 14.1.2.0.0 installation, not by moving to a new release number. To confirm a system is protected, check that the patch listed in CPU450 for your release is present (for example, in your OPatch inventory). The product version string alone does not tell you whether the fix is installed. Patch downloads require a My Oracle Support login.

Temporary measures and their limits

Oracle's advisory notes that, where patching cannot happen immediately, blocking the network protocols required by an attack (HTTP for this CVE) or removing privileges from users who do not need them may reduce the risk of successful attack. Oracle also warns that both approaches may break application functionality, should be tested on nonproduction systems, and do not correct the underlying problem. The reviewed material contains no CVE-specific URL filter, firewall rule, or list of MFT roles that neutralize the issue.

Database lag

At the time of writing, OpenCVE showed "No remediation available yet" and the NVD record was still in the "Received" state. That lag does not mean a patch is missing. Oracle's advisory and CSAF record are the authoritative sources, and both confirm the vendor fix.

Affected systems and versions

  • Product: Oracle Managed File Transfer (Oracle Fusion Middleware)
  • Component: MFT Runtime Server
  • Affected supported versions: 12.2.1.4.0 and 14.1.2.0.0
  • Vulnerable configuration: the MFT Runtime Server reachable over HTTP by an attacker holding low privileges on the deployment
  • Still vulnerable: installations at 12.2.1.4.0 or 14.1.2.0.0 that have the October 2026 CPU but not the November 2026 CSPU patch from CPU450

Oracle provides these patches for versions under Premier Support or Extended Support and states that unsupported releases are not tested for the vulnerabilities addressed in the update, so older releases should not be assumed unaffected.

Vendor security history

Oracle maintains a regular patch cadence of quarterly CPUs supplemented by CSPUs. MFT Runtime Server itself received fixes in the October 2026 CPU (including CVEs related to Apache Mina) only a month before this CSPU.

Oracle's advisory also states that it continues to receive reports of attempts to exploit vulnerabilities that already have patches, including successful attacks against customers who had not applied them. That points to slow patch deployment in the installed base as a recurring risk, rather than a lack of vendor fixes.

A relevant precedent from another Oracle product is CVE-2025-61882 in Oracle EBS. On October 6, 2025, the UK NCSC confirmed active exploitation, described potential remote code execution, and recommended a compromise assessment, installation of the EBS update, and continuous monitoring and threat hunting. That case involves a different product, vulnerability, and set of prerequisites, and its indicators should not be applied to CVE-2026-114827. It is useful mainly as a contrast. For EBS there was confirmed campaign evidence, while for this MFT issue the public record currently establishes severity and impact but not exploitation.

References

Detect & fix
what others miss

Works with
  • GitHub
  • GitLab
  • Bitbucket
  • Azure DevOps Services
  • Gerrit
  • CVS
  • Jira
  • Linear
  • Slack
  • Security Compass
Explore integrations
Security magnifying glass visualization