Automated Threat Modeling

Quick Look: Oracle iProcurement CVE 2026 114897, an Authenticated Redirection Flaw That Allows Application Takeover

A brief summary of CVE 2026 114897, a High-severity (CVSS 8.8) flaw in the Redirection component of Oracle iProcurement 12.2.3 through 12.2.15 that lets a low-privileged user take over the application over HTTP. Includes Oracle's November 2026 CSPU patch information and the current, unconfirmed exploitation status.

CVE Analysis

8 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-17

Quick Look: Oracle iProcurement CVE 2026 114897, an Authenticated Redirection Flaw That Allows Application Takeover

Introduction

A newly patched flaw in the Redirection component of Oracle iProcurement allows any attacker holding a low-privileged account to take over the application over HTTP. No other user has to click a link or approve anything. iProcurement sits inside the purchasing workflows of Oracle E Business Suite, where requisitions move through approvals, purchase orders, receipts, invoices, and payments. Oracle's High rating for confidentiality, integrity, and availability therefore applies to a business-critical process, not a peripheral web page.

Oracle iProcurement is a purchasing application within Oracle E Business Suite (EBS) that gives internal corporate requesters a shopping interface for ordering from local and external catalogs and for managing requisitions. Oracle states that thousands of organizations worldwide rely on EBS for core business operations spanning financial management, human capital management, procurement, and supply chain management. That footprint makes EBS components a regular subject of Oracle's security releases and, historically, a target for attackers interested in enterprise data.

Technical information

What Oracle has disclosed

Oracle's November 2026 risk matrix lists CVE 2026 114897 against Oracle iProcurement, component Redirection, protocol HTTP, with supported versions 12.2.3 through 12.2.15 affected. The authentication column indicates the flaw is not remotely exploitable without authentication, and the description explicitly requires a low-privileged attacker. The stated outcome is takeover of Oracle iProcurement.

The published CVSS 3.1 vector is:

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

Read against the FIRST CVSS 3.1 specification, the values mean:

  • Attack Vector: Network. Exploitation is possible over a network. FIRST allows this value even when the network is an intranet, so an internally hosted EBS deployment is not automatically outside the attack model.
  • Attack Complexity: Low. No specialized access conditions or extenuating circumstances are required.
  • Privileges Required: Low. The attacker needs basic privileges in the application first. A fully unauthenticated external attacker does not meet this condition.
  • User Interaction: None. Exploitation does not depend on a victim's participation.
  • Scope: Unchanged. The assessed impact stays within the security authority of the vulnerable component.
  • Confidentiality, Integrity, Availability: High. Oracle assigns High to all three, which is what drives the 8.8 score.

The 8.8 base score places the issue in FIRST's High severity band. A base score measures intrinsic severity. On its own, it says nothing about whether attacks are occurring.

Root cause: what is and is not known

EBS is closed source, and Oracle has published no commit, diff, vulnerable URL, request parameter, payload, request sequence, or explanation of how the defect produces takeover. The only public technical detail is the component name, Redirection. VulDB likewise states that technical details and a public exploit are unavailable.

The component name alone does not establish a specific authentication bypass, server-side request forgery technique, or remote code execution chain, and we are not going to reconstruct one. Oracle's description also does not claim operating system compromise. The documented impact is at the application level, and response decisions should preserve that scope.

The patch notes we reviewed suggest the fix tightens how iProcurement checks or authorizes redirect targets and parameters for authenticated users. That is our inference. Oracle has not confirmed it.

Attack flow based on the published conditions

Within the limits of Oracle's disclosure, the attack conditions are:

  1. The attacker holds a low-privileged account that can authenticate to iProcurement.
  2. The attacker reaches the iProcurement application over HTTP from any network position that can reach it, including an internal network. Under Oracle's advisory convention, a listed HTTP protocol also implies HTTPS is affected.
  3. The attacker exploits the Redirection component directly. Attack complexity is low and no other user needs to take any action.
  4. Successful exploitation can result in takeover of Oracle iProcurement, with High impact to confidentiality, integrity, and availability within the component's scope.

The specific requests involved in step 3 are not public.

Conflicting third-party classification

VulDB assigns CWE 601, URL Redirection to Untrusted Site (Open Redirect). This is a secondary classification. Oracle's published description does not state a CWE, and the generic CWE 601 definition does not explain how this particular defect achieves application takeover.

VulDB's narrative also states that authentication is unnecessary and that victim interaction is required. Both statements contradict Oracle's PR:L and UI:N values. We treat Oracle's original risk matrix and description as the authoritative basis for the attack conditions.

The publication record has a gap as well. Oracle's advisory records an initial release on 17 November 2026, and VulDB records disclosure on the same date, but at the time of the briefing the NVD page for this CVE returned "CVE ID Not Found". That gap does not negate Oracle's explicit entry.

Patch information

Fix vehicle: November 2026 Critical Security Patch Update

Oracle fixed CVE 2026 114897 in its November 2026 Critical Security Patch Update (CSPU), released on 17 November 2026 as "Rev 1. Initial Release". The fix appears in the advisory's Oracle E Business Suite risk matrix:

  • Product: Oracle iProcurement (Oracle E Business Suite)
  • Component: Redirection
  • Versions covered by the fix: 12.2.3 through 12.2.15
  • CVSS 3.1: 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H)

NVD's record for the CVE points only to this Oracle advisory, so the advisory is the authoritative patch reference.

What the machine-readable advisory says

Oracle's CSAF file for the November 2026 CSPU (tracking version 1, current release date 17 November 2026) is the clearest evidence that a fix exists. For this CVE it lists:

  • Product status: known_affected for Oracle iProcurement Version 12.2.3 through 12.2.15.
  • Remediation category: vendor_fix, meaning a real code fix rather than a workaround or a "no fix planned" entry.
  • Remediation details: available to Oracle customers with valid support contracts.
  • Remediation URL: My Oracle Support document KA923.

Finding the right patch: My Oracle Support Note KA923

Oracle does not publish EBS fixes as public downloads or diffs. The advisory states that the November CSPU contains 71 new security patches for Oracle E Business Suite, 19 of them for vulnerabilities that may be remotely exploitable without authentication. This CVE is not one of those 19, because it requires a low-privileged login.

For exact patches, Oracle directs customers to the Oracle E Business Suite Release 12 Critical Security Patch Update Knowledge Document (November 2026), My Oracle Support Note KA923. That document maps each EBS release level from 12.2.3 through 12.2.15 to the patch numbers required, and reading it requires a support login. The specific iProcurement patch number is not publicly visible. The third-party tracker InfraStack also reported that it could not read the number behind the MOS login.

No single fixed product version is published for this CVE, and 12.2.15 is itself inside the affected range. Being on the latest 12.2 release level is not evidence of remediation.

CSPU versus CPU: why the schedule matters

This is a monthly Critical Security Patch Update, not a quarterly Critical Patch Update. Oracle describes CSPUs as monthly releases that deliver targeted, high-priority security fixes in a smaller package, supplementing the cumulative quarterly CPUs. In practice:

  • The fix arrived outside the normal quarterly cycle. Teams that patch EBS only quarterly could miss it until the next quarterly CPU on 19 January 2027.
  • The advisory lists upcoming dates of 15 December 2026 (CSPU), 19 January 2027 (CPU), 16 February 2027 (CSPU), and 16 March 2027 (CSPU). Check KA923 again around these releases in case the iProcurement fix is superseded or reissued.

Verifying the fix

Because no code is public, defenders cannot confirm the fix by inspecting it. Confirm remediation by checking that the patches KA923 lists for your EBS 12.2 release level are recorded as applied in your patch inventory.

Database and middleware dependencies

Oracle's advisory notes that EBS includes Oracle Database and Oracle Fusion Middleware components whose security updates are not included in the EBS risk matrix, with exposure depending on the component versions in use. Oracle recommends applying the November 2026 updates to those underlying components as well. Addressing the iProcurement entry is not the same as addressing every vulnerability in the full EBS deployment.

Oracle's interim guidance

Until the patch is applied, Oracle says risk may be reduced by:

  • Blocking the network protocol the attack requires, here HTTP. Since HTTPS is treated as affected when HTTP is listed, moving from HTTP to HTTPS is not a remediation.
  • Removing privileges or package access from users who do not need them, for attacks that depend on those privileges.

Oracle warns that both approaches can break application functionality, that they should be tested outside production, and that neither corrects the underlying problem. The reviewed material identified no WAF signature or configuration workaround specific to this CVE. Applying the CSPU patch is the only real fix.

Affected systems and versions

  • Product: Oracle iProcurement, part of Oracle E Business Suite
  • Component: Redirection
  • Affected supported versions: 12.2.3 through 12.2.15 (inclusive, so 12.2.15 is affected)
  • Protocol: HTTP (HTTPS is also considered affected under Oracle's advisory convention)
  • Preconditions: the attacker must hold a low-privileged account and have network access to the application. No user interaction is needed.
  • Related components to review: the Oracle Database and Oracle Fusion Middleware components underlying EBS, which have their own November 2026 updates outside the EBS risk matrix

Vendor security history

Oracle states that it continues to receive reports of attempts to exploit vulnerabilities for which patches already exist, and that some successful attacks involved customers who had not applied available patches. Oracle recommends running actively supported versions and patching without delay. The 71 EBS patches in this single monthly release show the volume of remediation work and why EBS patch planning has to account for multiple components, although patch counts alone do not establish a comparative failure rate.

The platform also has a recent history of exploitation before a patch existed. Google Threat Intelligence Group and Mandiant began tracking a large-scale, CL0P-branded extortion campaign on 29 September 2025, in which executives received emails claiming theft of sensitive data from EBS environments. Google assessed that attackers may have exploited CVE 2025 61882, involving the EBS SyncServlet component and unauthenticated remote code execution, as early as 9 August 2025. In some cases significant data was exfiltrated. Oracle directed customers to apply emergency patches on 4 October 2025, and Google later assessed that servers updated through the 11 October patch were likely no longer vulnerable to the known exploitation chains. Google did not formally attribute the activity to a tracked group, noting that CL0P branding and tooling overlapped with FIN11 activity but were not exclusive to it.

Exploitation status of CVE 2026 114897

That campaign concerns a different vulnerability with different entry conditions. For CVE 2026 114897 specifically:

  • Confirmed exploitation in the wild: not established in the reviewed reporting.
  • Public proof of concept: VulDB reports none publicly available.
  • Threat actor attribution: none established.
  • Target-specific indicators of compromise: none identified.
  • CISA KEV status: inclusion could not be conclusively established from the retrieved catalog material, which is not the same as confirmed absence.

The absence of public exploit details limits what is known; it does not prove that private exploitation has not occurred. Equally, nothing in the sources links this iProcurement flaw to CL0P, FIN11, or the 2025 attack chain.

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