Automated Threat Modeling

Quick Look: Oracle Applications Framework CVE-2026-114917, an Authenticated Personalization Flaw Enabling Framework Takeover in Oracle EBS 12.2

A brief summary of CVE-2026-114917, a CVSS 8.8 flaw in the Personalization component of Oracle Applications Framework (Oracle EBS 12.2.3 through 12.2.15) that lets a low-privileged attacker take over the framework over HTTP. Includes Oracle's November 2026 CSPU patch details and the bug ID to verify the fix.

CVE Analysis

8 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-17

Quick Look: Oracle Applications Framework CVE-2026-114917, an Authenticated Personalization Flaw Enabling Framework Takeover in Oracle EBS 12.2

Introduction

A newly patched flaw in the Personalization component of Oracle Applications Framework gives an attacker who already holds a low-privileged account on an Oracle EBS 12.2 system a network path to taking over the framework itself. Oracle EBS runs financials, procurement, human capital and supply chain operations for many enterprises, so an application-layer takeover in this stack is a business concern as much as a technical one.

Oracle Applications Framework (OAF) is a product within Oracle EBS, Oracle's suite of integrated business applications spanning financial management, human capital management, procurement, customer relationship management, projects and supply chain. Oracle states that thousands of organizations around the world rely on EBS for key business operations, and the 12.2 line has Premier Support extending through at least 2037. The affected Personalization component, documented as the OA Personalization Framework, lets organizations tailor application pages without modifying underlying code. That makes it a familiar customization surface in long-lived EBS deployments.

Technical information

What Oracle disclosed

Oracle, acting as the CVE Numbering Authority, published CVE-2026-114917 on November 17, 2026 as part of its November 2026 Critical Security Patch Update (CSPU). The official description says the vulnerability is easily exploitable, allows a low-privileged attacker with network access via HTTP to compromise Oracle Applications Framework, and that successful attacks can result in takeover of Oracle Applications Framework.

The published vector is:

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

Broken down:

  • AV:N: reachable over the network (HTTP)
  • AC:L: low attack complexity
  • PR:L: low privileges required
  • UI:N: no user interaction required
  • S:U: scope unchanged
  • C:H / I:H / A:H: high confidentiality, integrity and availability impact

The base score is 8.8 (High), supplied by Oracle. At the time of our review, NVD had not published an independent NIST assessment.

The most important detail in the vector is the privilege requirement, which is PR:L and not PR:N. The attacker needs an existing foothold in the form of a low-privileged account, so this is not an unauthenticated EBS bug. Requiring privileges does not lower the impact, though. The vector still assigns high impact across all three CIA dimensions.

How Personalization normally works

Oracle's documentation describes the OA Personalization Framework as a way to personalize application pages without modifying the underlying code. Personalizations are layered over base product metadata at runtime rather than overwriting the base interface. The documentation separates administrative personalization levels, which can apply to defined audiences, from user-level personalizations, which are visible only to the user who created them.

This tells us what the component is for, but it does not explain the defect. Nothing in the public material ties the vulnerability to a specific personalization level, metadata type or runtime behavior.

Root cause: what is and is not known

OAF is closed source, and Oracle has not published a commit, diff, changelog or technical writeup. Specifically:

  • No official CWE is assigned in the CVE or NVD records. VulDB separately labels the issue CWE-269 (Improper Privilege Management), but that is a secondary-source classification, not a vendor-disclosed root cause.
  • No vulnerable HTTP endpoint, request parameter, payload, function or required EBS responsibility has been disclosed.
  • Oracle does not say whether the fix tightens authorization checks, validates personalization metadata, or changes how personalizations are executed.

Given that, we are not going to label this as SQL injection, template injection, deserialization or any particular code execution primitive. The supported outcome is takeover of Oracle Applications Framework. The disclosure does not confirm a separate operating system or database takeover.

Attack flow based on published conditions

With no exploit mechanism disclosed, we can describe the attack flow only in terms of the published prerequisites and outcome:

  1. Foothold. The attacker holds a low-privileged account on the target EBS instance. Oracle does not disclose which responsibility or role is sufficient.
  2. Reachability. The attacker has network access to the EBS application tier over HTTP.
  3. Interaction with Personalization. The attacker sends requests that reach the vulnerable Personalization component. The vector rates this as low complexity and requiring no action by any other user.
  4. Outcome. Successful exploitation results in takeover of Oracle Applications Framework, with high impact to confidentiality, integrity and availability within an unchanged scope.

For exposure assessment, this means any population of low-privileged EBS users, including broad self-service user bases, is part of the relevant attacker pool. Network reachability of the EBS web tier is the other condition that matters.

Exploitation status

The reviewed official CVE and NVD records do not establish active exploitation, public exploit code, a named threat actor or CVE-specific indicators of compromise. VulDB lists KEV status as no, although official CISA catalog membership was not conclusively established in the material we reviewed. We located no confirmed evidence of exploitation, but that does not show exploitation is impossible. Oracle's November 2026 advisory also notes, as a vendor-wide observation unrelated to any specific CVE, that it continues to see attempts to exploit vulnerabilities for which patches already exist, and that some attacks succeeded because customers had not applied available patches.

Patch information

Oracle fixed CVE-2026-114917 in its November 2026 Critical Security Patch Update (CSPU), with the first revision of the advisory published on November 17, 2026. The issue appears in the Oracle EBS Risk Matrix with a CVSS 3.1 base score of 8.8.

How the fix is delivered

Because OAF is closed source, the only fix details come from Oracle's own advisory artifacts:

  • Tracking ID: The machine-readable CSAF file for the November 2026 CSPU links this CVE to Oracle Bug ID 39648003 ("Oracle Bug ID of Oracle Applications Framework").
  • Remediation type: The CSAF marks the remediation as vendor_fix, limited to Oracle customers with valid support contracts, and points to My Oracle Support document KA923.
  • Patch selection document: The HTML advisory directs EBS customers to My Oracle Support Note KA923, the Oracle EBS Release 12 Critical Security Patch Update Knowledge Document (November 2026). That note maps each 12.2.x code level to the specific OAF patch it needs. Oracle does not publish those patch numbers or a fixed version string.

What this means in practice

The fix is a patch rather than a version upgrade, and no release fixes it simply by being installed. You apply the November 2026 CSPU patch for OAF that KA923 lists for your exact EBS 12.2 code level. To confirm the fix is present, check that bug 39648003 appears among the bugs fixed in your applied patch inventory. A version number check will not tell you.

Oracle also notes that EBS includes Oracle Database and Oracle Fusion Middleware components. Vulnerabilities in those components are listed in their own sections of the same advisory, and an EBS system's exposure depends on the Database and Fusion Middleware versions it runs. Oracle therefore recommends applying the November 2026 CSPU to those tiers as well. Patching only the OAF application tier addresses this CVE but can leave related findings from the same advisory unfixed.

Interim measures and their limits

Oracle's advisory describes generic risk-reduction options for customers who cannot patch immediately, such as blocking network protocols required by an attack or removing privileges and package access an attack depends on. Oracle explicitly warns that these measures may break application functionality, should be tested on nonproduction systems first, and do not fix the underlying problem. For this CVE they are of limited precision, because Oracle has not disclosed which privilege is required. Patching remains the primary response.

Limits of the public evidence

The NVD entry did not resolve when we checked it during patch research, so the patch details above rely only on Oracle's materials. The patch binaries and KA923 are available only to licensed customers through My Oracle Support.

Affected systems and versions

  • Product: Oracle Applications Framework, part of Oracle EBS
  • Component: Personalization
  • Affected supported versions: 12.2.3 through 12.2.15, inclusive. Release 12.2.15 is inside the affected range and is not a remediation by itself.
  • Fixed state: No fixed version string exists. An environment is remediated once the November 2026 CSPU OAF patch that KA923 lists for its code level is applied, which you can verify by the presence of bug 39648003.
  • Exploitation preconditions: An authenticated low-privileged account plus HTTP network access to the EBS application tier.
  • Related tiers: Oracle Database and Oracle Fusion Middleware components bundled with EBS are covered by separate entries in the same advisory and should be patched alongside the application tier.
  • Older releases: Oracle provides security patches only for versions under Premier Support or Extended Support, and the advisory lists supported versions only. Releases outside that window are not addressed by the advisory.

Vendor security history

Oracle EBS has a recent, well-documented history of serious exposure. Google Threat Intelligence Group and Mandiant reported an extortion campaign in which an actor claiming affiliation with the CL0P brand, beginning September 29, 2025, emailed executives alleging theft of sensitive data from EBS environments. Google assessed that the activity may have involved zero-day exploitation of CVE-2025-61882, which the UK NCSC described as an unauthenticated remote vulnerability, and documented significant data exfiltration in some cases. Oracle released a patch on October 4, 2025, and Google later assessed that EBS servers updated through the October 11 patch were likely no longer vulnerable to the known exploitation chains.

Google explicitly did not formally attribute that activity to a tracked threat group and cautioned that CL0P branding is not used exclusively by FIN11. That campaign involved a different CVE with different prerequisites (unauthenticated, versus the low-privileged access required here). It gives useful business context about the consequences of EBS compromise, but it is not evidence that CVE-2026-114917 is being exploited, and it gives no basis to attribute this CVE to any actor.

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