Automated Threat Modeling

Overview of CVE-2026-114925: Unauthenticated Takeover Risk in Oracle EBS Applications Framework REST Services

A brief summary of CVE-2026-114925, a CVSS 9.8 unauthenticated vulnerability in the REST Services component of Oracle Applications Framework in Oracle EBS 12.2.3 through 12.2.15, including Oracle's November 2026 patch guidance.

CVE Analysis

7 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-17

Overview of CVE-2026-114925: Unauthenticated Takeover Risk in Oracle EBS Applications Framework REST Services

Introduction

An unauthenticated attacker who can reach the REST Services layer of Oracle Applications Framework over HTTP may be able to take over the framework that sits inside Oracle's EBS application suite. Oracle rates the issue 9.8 under CVSS 3.1 and fixed it in the November 2026 Critical Security Patch Update, so teams running EBS 12.2 should treat exposure review and patch verification as a near-term task.

Oracle EBS (Oracle's E Business Suite) is an enterprise applications suite that Oracle describes as supporting thousands of organizations around the world in key business operations. Its documentation lists functions spanning customer relationship management, service management, financial management, human capital management, project portfolio management, advanced procurement, supply chain management, value chain planning and value chain execution. Oracle Applications Framework is the framework product within EBS that this CVE affects, and the vulnerable component is its REST Services interface.

Technical Information

What Oracle disclosed

Oracle lists CVE-2026-114925 in the Oracle EBS risk matrix of its November 2026 Critical Security Patch Update (CSPU). The relevant fields are:

  • Product / component: Oracle Applications Framework / REST Services
  • Protocol: HTTP
  • Remotely exploitable without authentication: Yes
  • CVSS 3.1: 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)
  • Affected (pre-patch) supported versions: 12.2.3 through 12.2.15
  • Internal Oracle bug ID: 40230872 (Oracle Applications Framework)

Oracle's description calls this an easily exploitable vulnerability that allows an unauthenticated attacker with network access via HTTP to compromise Oracle Applications Framework, and states that successful attacks can result in takeover of Oracle Applications Framework.

Reading the CVSS vector

Because Oracle has not published implementation details, the vector is the most concrete technical description available:

  • AV:N: the attack is network based.
  • AC:L: attack complexity is low.
  • PR:N: no privileges or valid account are required.
  • UI:N: no user interaction is required.
  • S:U: the security impact stays within the vulnerable component's scope.
  • C:H / I:H / A:H: high impact to confidentiality, integrity and availability.

In defensive terms, any EBS instance whose OAF REST Services surface is reachable over HTTP, whether from the internet or from internal networks, deserves review, because the stated scenario does not require credentials. The record does not specify any network exposure configuration beyond HTTP network access.

Root cause: not publicly documented

Oracle's risk matrix entry does not explain the underlying defect, the affected REST operation, the vulnerable request fields or a reproduction sequence. The CVE record provides access conditions and impact but no code-level details, and it assigns no CWE. EBS is closed source, so there is no public commit or diff to examine.

VulDB categorizes the issue as privilege management and associates CWE-269 and CWE-266. That is a third-party classification, not one stated by Oracle or the CVE record, and VulDB itself reports that technical details are unknown. We therefore make no claim about a specific code defect, endpoint or exploit chain.

Attack flow as described by the public record

Based only on the official description and vector, the exploitation scenario looks like this:

  1. An attacker has network access via HTTP to an EBS 12.2.3 through 12.2.15 instance exposing Oracle Applications Framework REST Services.
  2. The attacker needs no account, no privileges and no action from a legitimate user.
  3. Exploitation is rated low complexity, meaning no special conditions beyond reachability are described.
  4. A successful attack can result in takeover of Oracle Applications Framework, with high impact to confidentiality, integrity and availability.

The specific requests involved are not public, so no endpoint-level signature can be derived from the available sources.

Exploitation status and record discrepancies

At the time of the reviewed reporting, a vulnerability tracker stated "NO KNOWN EXPLOIT" and "No reports of exploitation as of Nov 17," and VulDB stated no public exploit was available. These observations are bounded by their reporting dates and do not rule out private or unreported activity. No threat actor attribution or indicators of compromise were found, and CISA KEV status was not established from the reviewed sources.

One record discrepancy matters for triage. CVE.org lists the record as published on November 17, 2026, but the NVD page retrieved during review returned "CVE ID Not Found." Oracle's text-form risk matrix independently confirms the component, versions and attack vector, so the mismatch reduces database corroboration rather than casting doubt on the vulnerability.

Patch Information

Where the fix lives

Oracle fixed CVE-2026-114925 in its November 2026 Critical Security Patch Update, released on 17 November 2026. Everything public about the fix comes from Oracle's advisory, its text-form risk matrix and its machine-readable CSAF file.

The internal bug ID 40230872 is the most useful artifact for verification. When reviewing Oracle patch readmes or inventory reports, search for bug 40230872 to confirm the fix for this CVE is actually installed. That is a stronger check than knowing that "the November patch" was applied.

What the CSAF record says

Oracle's November 2026 CSAF file records the remediation with category vendor_fix, details "Oracle customers with valid support contracts", a product ID covering the 12.2.3 through 12.2.15 range, and a URL pointing to support document KA923. That tells us three things:

  • The remediation is a vendor fix rather than a workaround.
  • It applies to the whole 12.2.3 through 12.2.15 range. Oracle does not name a fixed EBS release, so upgrading to a newer 12.2.x code level does not remove the need for the CSPU patch.
  • Download requires a support login. The advisory is public, but patch files are only available to customers with a valid Oracle support contract on My Oracle Support (MOS).

How to get the right patches

For EBS, Oracle does not publish patch numbers in the advisory. It points instead to MOS Note KA923, titled in the advisory as the Oracle E Business Suite Release 12 Critical Security Patch Update Knowledge Document (November 2026). Oracle's EBS Technology blog describes KA923 as the bookmarkable entry point to the latest monthly and quarterly EBS CPU/CSPU documents. In practice:

  1. Open KA923 on MOS and follow it to the November 2026 EBS CSPU availability document.
  2. Find the Oracle Applications Framework (FND/OAF) patch matching your exact 12.2.x code level and download it.
  3. Apply it as a normal 12.2 patch with AD Online Patching (adop), then confirm bug 40230872 shows as applied.

The EBS blog also advises reading the supporting documents linked from the advisory before applying patches, because prerequisites differ by code level.

Patch the whole stack

Oracle notes that EBS exposure also depends on the Oracle Database and Oracle Fusion Middleware versions underneath it, and that fixes for those components are not shown in the EBS risk matrix. Oracle recommends applying the November 2026 CSPU to those components too. Patching only the OAF layer addresses this CVE but can leave other November fixes missing from the same deployment. For scale, the advisory reports 71 new EBS security patches in this update, 19 of which may be remotely exploitable without authentication. Those totals describe the full update, not this CVE alone. The executive summary for the whole November release is MOS Doc ID CPU433.

Reducing exposure before patching

Oracle's general guidance is that blocking network protocols required by an attack may reduce risk before patches are applied. Since this CVE's disclosed attack path is HTTP, reviewing and restricting HTTP reachability to affected EBS services is a reasonable interim step. Oracle does not specify a CVE-specific rule, endpoint or port. It warns that blocking protocols or removing privileges can break application functionality, recommends testing such changes on nonproduction systems, and states that these measures do not fix the underlying problem.

What we cannot see

Oracle has not published technical details of the code change, such as which REST Services endpoint or authentication check was fixed. Treat any claim about the exact code-level change as speculation unless Oracle publishes more.

Affected Systems and Versions

  • Product: Oracle Applications Framework in Oracle EBS
  • Component: REST Services
  • Affected supported versions: 12.2.3 through 12.2.15
  • Exposure condition: network access to the affected service via HTTP, with no authentication or user interaction required
  • Fixed in: November 2026 CSPU patch for Oracle Applications Framework (bug 40230872). No fixed EBS release is named, so the CSPU patch is required at every 12.2.x code level in the range.
  • Unsupported releases: Oracle states that releases outside Premier Support or Extended Support are not tested for vulnerabilities covered by the update and that earlier versions may also be affected. Obtain version-specific guidance from Oracle for installations outside the listed range or support window.
  • Related components: the underlying Oracle Database and Oracle Fusion Middleware installations should receive the November 2026 CSPU as well

Vendor Security History

The most relevant prior event is CVE-2025-61882, a different EBS vulnerability. Google Threat Intelligence Group reported that threat actors may have exploited it as a zero day against EBS customers as early as August 9, 2025, before a patch was available, with suspicious activity dating to July 10, 2025. Oracle directed customers to apply emergency patches on October 4, 2025, and in some cases attackers exfiltrated a significant amount of data. GTIG had not formally attributed that activity to a tracked group at the time of its report and cautioned that use of the CL0P extortion brand could not alone support attribution to FIN11.

This history shows that EBS vulnerabilities have previously had serious operational consequences. It does not establish exploitation of CVE-2026-114925, and its indicators and attribution should not be transferred to this CVE.

On process, Oracle states that Critical Patch Updates are its primary mechanism for delivering security fixes for on-premises products, are released quarterly, and may be supplemented by out-of-schedule Security Alerts for particularly critical vulnerabilities or reported in-the-wild exploitation. The reviewed sources do not provide enough comparative data to assess Oracle's overall security track record.

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