Automated Threat Modeling

Brief Summary: CVE-2026-114924, Unauthenticated Takeover of Oracle EBS Application Object Library (CVSS 9.8)

A brief summary of CVE-2026-114924, a CVSS 9.8 flaw in the Core component of Oracle Application Object Library that lets an unauthenticated attacker with HTTP access take over the component on Oracle EBS 12.2.3 through 12.2.15. It covers the known technical facts, patch information from the November 2026 CSPU, affected versions and relevant vendor history.

CVE Analysis

7 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-17

Brief Summary: CVE-2026-114924, Unauthenticated Takeover of Oracle EBS Application Object Library (CVSS 9.8)

Introduction

Oracle's November 2026 Critical Security Patch Update includes a fix for a flaw that lets an unauthenticated attacker with HTTP access take over Oracle Application Object Library, the shared foundation that every Oracle E Business Suite (EBS) module relies on. Application Object Library supplies sign-on, session handling, profiles and access control through responsibilities across the whole suite. A takeover of this component therefore matters to any organization running EBS 12.2 for finance, supply chain or HR operations.

Oracle rates CVE-2026-114924 at CVSS 3.1 9.8 (Critical). This summary covers what Oracle and other public sources have disclosed, what remains unknown, and how the fix is delivered.

Technical information

What is disclosed

The vulnerability sits in the Core component of Oracle Application Object Library (FND). Oracle publishes the following CVSS 3.1 vector:

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

Breaking that down:

  • Attack Vector: Network. Oracle identifies HTTP as the attack protocol.
  • Attack Complexity: Low. Oracle describes the issue as easily exploitable.
  • Privileges Required: None. No existing EBS account is needed.
  • User Interaction: None. No other user has to take any action.
  • Scope: Unchanged. Impact is scored within the vulnerable component's security scope. Unchanged scope does not mean low impact.
  • Confidentiality, Integrity, Availability: High. The stated outcome is takeover of Oracle Application Object Library.

Per FIRST's CVSS guidance, a Base score expresses intrinsic technical severity. It is not evidence of a public exploit or an active campaign.

Why the component matters

Oracle's documentation describes Application Object Library as reusable code, programs and database objects that provide common functionality across EBS products, including security administration and concurrent processing. It also controls access through user sign-ons and responsibilities, which is why a takeover of this layer is significant. The public disclosures do not, however, state that this CVE bypasses every responsibility boundary, compromises every business module, or extends to the operating system or database.

Root cause: not publicly disclosed

EBS is closed source, and Oracle has published no commit, diff or code-level description. The official CVE record carries no CWE. VulDB describes the flaw as involving an unknown function and unknown input, and assigns CWE-269 (Improper Privilege Management) while also listing CWE-266. These are third-party classifications, not an Oracle-stated root cause. VulDB also states that neither technical details nor an exploit are publicly available.

We therefore cannot responsibly label this as SQL injection, deserialization, command injection or any specific defect class, and we are not providing code snippets or endpoints because none have been published.

Attack flow (as far as public sources allow)

The disclosed attack model is limited but clear:

  1. An attacker has network access to an EBS 12.2.3 through 12.2.15 instance over HTTP.
  2. Without authenticating and without any user interaction, the attacker sends requests that reach the vulnerable Core component of Application Object Library.
  3. A successful attack results in takeover of Application Object Library, with high impact to confidentiality, integrity and availability.

The specific request structure, payload and exploitation sequence have not been disclosed.

Exploitation status

As of November 18, 2026, we found no public reporting confirming active exploitation of CVE-2026-114924 or attributing it to a named actor. The CVE was not present in the CISA Known Exploited Vulnerabilities catalog version 2026.11.17, released November 17, 2026. That snapshot is not proof of nonexploitation. Nor should the lack of a public exploit be read as evidence that exploitation is difficult, since Oracle rates the attack complexity as Low.

Patch information

Oracle fixed CVE-2026-114924 in its November 2026 Critical Security Patch Update (CSPU), released November 17, 2026. Because Application Object Library underpins every EBS module, this fix covers the whole EBS stack rather than a single product.

What the vendor fix is

Oracle's machine-readable CSAF advisory lists the CVE as follows:

  • Remediation category: vendor_fix, an actual code fix rather than a workaround.
  • Oracle Bug ID: 40182955, for tracking the fix in My Oracle Support (MOS) and confirming it is applied.
  • Affected product range: EBS 12.2.3 through 12.2.15, so every supported 12.2 release level needs the patch.
  • Remediation URL: MOS knowledge document KA923, Oracle E Business Suite Release 12 Critical Security Patch Update Knowledge Document (November 2026).
  • Availability: Oracle customers with valid support contracts. The advisory is public, but downloading patches requires a MOS login.

This CVE is one of four EBS issues in this release rated 9.8 that need no login. In total, the CSPU includes 71 new security patches for EBS, 19 of which are remotely exploitable without authentication.

How the fix is delivered

Oracle ships the fix as binary and application patches through MOS, not as a single universal download. KA923 is a routing document that maps your EBS release and code level to the correct patches:

  1. Determine your exact EBS 12.2.x release and current patch level.
  2. Use MOS Note KA923 to identify the November 2026 EBS CSPU patches for that level, including the one carrying the fix for Bug 40182955.
  3. Apply them with the normal EBS 12.2 patching process.

The underlying tech stack

EBS includes Oracle Database and Oracle Fusion Middleware components, and fixes for those do not appear in the EBS risk matrix. Oracle instructs customers to also apply the November 2026 CSPU to the Database and Fusion Middleware components of their EBS installation. Complete remediation means patching Application Object Library, which closes CVE-2026-114924, and also bringing the tech stack to the same CSPU level, as KA923 describes.

Verifying the fix

With no code-level details published, verification is administrative. Confirm that the November 2026 CSPU patches named in KA923, including the one for Bug 40182955, appear as applied in your EBS patch history. Treat any 12.2.x instance without the November 2026 CSPU as unpatched.

Interim measures and their limits

Oracle notes that blocking network protocols required by an attack may temporarily reduce risk until patches are applied, but this can break application functionality, should be tested on nonproduction systems first, and does not correct the underlying defect. Oracle's general advice about removing unnecessary privileges applies to attacks that require privileges; since this flaw requires none, privilege reduction is not an established mitigation here.

Affected systems and versions

  • Product: Oracle Application Object Library (FND), part of Oracle EBS
  • Component: Core
  • Affected supported versions: 12.2.3 through 12.2.15 (every supported 12.2 release level)
  • Exposure condition: network access to the application over HTTP, with no authentication or user interaction required
  • Fixed in: November 2026 Critical Security Patch Update (Bug 40182955), per MOS Note KA923

Oracle recommends upgrading unsupported releases to supported versions, because unsupported releases are not tested against the vulnerabilities in the update. The published affected range should not be read as proof that older unsupported releases are safe.

Vendor security history

Oracle documents a Software Security Assurance program covering secure coding standards, mandatory developer security training, security leaders, and automated analysis and testing, with remediation delivered through Critical Patch Updates and Security Alerts. These are stated practices rather than independently measured results.

EBS has a recent record of real-world exploitation. CVE-2025-61882, a different vulnerability in BI Publisher Integration within Oracle Concurrent Processing, was reported by the UK NCSC as actively exploited, with crafted unauthenticated HTTP requests able to cause full system compromise. Google Threat Intelligence documented significant data exfiltration at some affected organizations, and Oracle issued emergency patches on October 4, 2025. Google noted it had not formally attributed that activity to a tracked group. Oracle's November 2026 advisory also reports successful attacks against customers who had not applied available patches.

That history concerns a different component and CVE. It is useful context for prioritization, but it does not establish exploitation or attribution for CVE-2026-114924.

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