Automated Threat Modeling

Quick Look: CVE-2026-114911, an Unauthenticated Integrity Flaw in Oracle iProcurement Approval List and Workflow

A brief summary of CVE-2026-114911, a CVSS 7.5 flaw in the Approval List and Workflow component of Oracle iProcurement that lets an unauthenticated attacker over HTTP create, modify, or delete critical data. Includes patch information from Oracle's November 2026 Critical Security Patch Update.

CVE Analysis

6 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-17

Quick Look: CVE-2026-114911, an Unauthenticated Integrity Flaw in Oracle iProcurement Approval List and Workflow

Introduction

Procurement approval chains exist so that purchases are reviewed before an organization commits money. A flaw Oracle patched in November 2026 sits directly in that control path. According to Oracle, an unauthenticated attacker with HTTP access to Oracle iProcurement could create, delete, or modify critical data handled by the Approval List and Workflow component.

Oracle iProcurement is a module of Oracle EBS, Oracle's enterprise application suite covering customer and service management, financial management, human capital management, project management, procurement, and supply chain functions. Oracle states that thousands of organizations worldwide rely on EBS for key business operations. Within iProcurement, the requisition approval workflow starts when a requisition is submitted, and a related workflow manages automatic creation of purchasing documents. That places the affected component close to how purchases are authorized and turned into orders.

Technical information

What Oracle disclosed

Oracle's November 2026 risk matrix describes CVE-2026-114911 as follows:

  • Product: Oracle iProcurement (Oracle EBS)
  • Component: Approval List and Workflow
  • Protocol: HTTP
  • Remote exploit without authentication: Yes
  • CVSS 3.1 base score: 7.5
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
  • Affected supported versions: 12.2.3 through 12.2.15

In the vector, the attack is network based and low complexity, needs no privileges and no user interaction, and leaves scope unchanged. Integrity impact is High, while confidentiality and availability are rated None. Oracle's description states that successful attacks can result in unauthorized creation, deletion or modification access to critical data or all Oracle iProcurement accessible data. VulDB independently lists the same score and vector and describes the issue as remotely exploitable without authentication.

Root cause

Oracle has not published root cause details, and no CWE is assigned in the NVD data or the reviewed advisory. VulDB titles its entry "Oracle iProcurement Approval List/Workflow privileges management", but the same record states that technical details are unknown, so that label is not enough to pin down the precise defect. There is no public commit, diff, or code for this closed-source fix, so we are not showing any vulnerable code.

The metadata does show the shape of the problem. An operation in the approval list and workflow area that changes data can be reached over HTTP without any authenticated session. Going by Oracle's patch notes (summarized below), the fix most likely adds missing authentication or authorization checks to approval list and workflow operations. That is an inference from the vulnerability description, not something Oracle has confirmed.

Why an integrity-only issue matters here

The iProcurement requisition approval workflow governs how submitted requisitions are approved, and a related workflow automatically creates purchasing documents. Unauthorized write access in this component therefore touches the data that procurement controls depend on. The sources do not describe a specific approval bypass, a particular altered transaction, or the exact data operation an attacker could perform, so we do not speculate about concrete fraud scenarios.

Attack flow (based on published metadata)

  1. The attacker identifies an Oracle iProcurement deployment running a version from 12.2.3 through 12.2.15 that is reachable over HTTP.
  2. The attacker sends requests to the Approval List and Workflow functionality without credentials. The specific endpoint or request format has not been made public.
  3. Because Oracle rates the issue as low complexity with no privileges and no user interaction required, an unpatched instance processes the request.
  4. The result is unauthorized creation, deletion, or modification of critical data or all Oracle iProcurement accessible data. Oracle records no confidentiality or availability impact.

Patch information

Oracle fixed CVE-2026-114911 in its November 2026 Critical Security Patch Update (CSPU), released on November 17, 2026 as Rev 1. This is a closed-source vendor fix with no public commit or diff. The details below come from Oracle's advisory, its CSAF record, and the text-form risk matrix.

What Oracle shipped

  • Product and component: Oracle iProcurement (part of Oracle EBS), component Approval List and Workflow.
  • Affected supported versions: 12.2.3 through 12.2.15. These are the affected releases, not fixed version numbers. In EBS 12.2 you obtain the fix by applying the patch on top of your current 12.2.x level, not by upgrading to a new release.
  • Oracle bug ID: 39496838. The CSAF record lists this under "Oracle Bug ID of Oracle iProcurement". It is the identifier to search for in My Oracle Support when checking whether the fix is installed.
  • Remediation type: the CSAF entry classifies the fix as vendor_fix for the affected iProcurement product range, with an availability note stating it is for "Oracle customers with valid support contracts".
  • Where to get it: both the advisory and the CSAF record point to the EBS patch availability document, My Oracle Support Note KA923, which maps each EBS 12.2.x baseline to the patches it needs. Downloads and install instructions require a support login.

How this fits Oracle's release cycle

The fix shipped in a Critical Security Patch Update rather than a quarterly Critical Patch Update (CPU). Oracle describes CSPUs as targeted, high-priority security fixes in a smaller, more focused format that sit alongside the quarterly cumulative CPUs rather than replacing them. In practice, you do not need to wait for the next quarterly CPU to close this flaw, but you should still maintain the regular quarterly CPU baseline.

EBS technology stack note

Oracle's advisory points out that EBS includes Oracle Database and Oracle Fusion Middleware components that may be affected by vulnerabilities listed in those sections of the same CSPU, and tells customers to apply the November 2026 CSPU to those components as well. Complete remediation therefore means:

  1. Applying the iProcurement application-tier patch for bug 39496838 as listed in KA923.
  2. Applying any applicable Database and Fusion Middleware patches from the same November 2026 CSPU.

To confirm the fix is in place, check for bug 39496838 in your EBS patch history, for example the AD_BUGS table or the adpatch and adop patch logs.

Interim measures

Until the patch is applied, Oracle notes that blocking the network protocols an attack requires may reduce risk. For this CVE, the matrix lists HTTP. Oracle warns that such restrictions can break application functionality, should be tested on systems not used in production first, and do not fix the underlying issue. Oracle's advice to remove user privileges applies to attacks that require privileges, which this one does not, so it should not be the primary control here.

Affected systems and versions

  • Product: Oracle iProcurement, part of Oracle EBS
  • Component: Approval List and Workflow
  • Affected supported versions: 12.2.3 through 12.2.15
  • Exposure condition: the iProcurement application reachable over HTTP by the attacker, with no authentication or user interaction required
  • Related components to assess: Oracle Database and Oracle Fusion Middleware components bundled with EBS, which Oracle says should receive the November 2026 CSPU updates as well

Oracle's advisory covers supported versions and makes no statements about versions outside that list.

Vendor security history

Oracle EBS has prior exploitation history that is useful context but must be kept separate from this CVE. Google Threat Intelligence Group reported earlier exploitation activity associated with CVE-2025-61882, and Google's guidance states that emergency EBS patches released on October 4, 2025 mitigated that activity. GTIG said it had not formally attributed that activity to a tracked threat group. Oracle's November 2026 advisory states that its patch for CVE-2026-114918 also addresses CVE-2025-61882.

None of this establishes exploitation or attribution for CVE-2026-114911. The reviewed sources do not confirm in-the-wild exploitation of this CVE, and VulDB reports that no exploit is available while also noting that technical details are unknown.

On process, Oracle publishes Critical Security Patch Updates on a schedule, makes them available to active support customers through My Oracle Support, and includes security fixes in patch sets and new product releases. Its November 2026 advisory notes that attackers have succeeded in some cases where customers had not applied available Oracle patches, and it recommends staying on actively supported versions and patching without delay.

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