Automated Threat Modeling

Brief Summary: Oracle iStore CVE-2026-114876, Unauthenticated Data Exposure in the Shopping Cart Component

A brief summary of CVE-2026-114876, an unauthenticated, network-exploitable confidentiality flaw in the Oracle iStore Shopping Cart component of Oracle E Business Suite 12.2.3 through 12.2.15, with notes on Oracle's November 2026 CSPU patch path.

CVE Analysis

7 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-17

Brief Summary: Oracle iStore CVE-2026-114876, Unauthenticated Data Exposure in the Shopping Cart Component

Introduction

An unauthenticated attacker with nothing more than HTTP access to an Oracle iStore deployment can obtain critical data, or all data that iStore can reach, through a flaw in its Shopping Cart component. Because Oracle scores the issue with a changed scope, the confidentiality impact may extend beyond iStore into other products in the same Oracle E Business Suite (EBS) environment.

Oracle iStore is the ecommerce application within Oracle EBS. It provides an internet sales channel for business-to-business and business-to-consumer commerce as part of Oracle's customer relationship management offering. Oracle documents iStore integrations covering inventory, pricing, order processing, credit card authorization, financials and procurement, and its functions include shopping carts, orders, invoices, payment details and quotes. We found no independent figures on iStore market share or deployment counts. Its relevance comes from Oracle's established position in enterprise applications and from how tightly iStore is connected to the rest of an EBS installation.

Technical information

What Oracle has disclosed

Oracle tracks this issue as CVE-2026-114876 in the Shopping Cart component of Oracle iStore, affecting supported releases 12.2.3 through 12.2.15. The CVSS 3.1 base score is 8.6 with the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N. Broken down:

  • Attack Vector: Network. Exploitation is possible over a network, via HTTP.
  • Attack Complexity: Low. Oracle describes the flaw as easily exploitable.
  • Privileges Required: None. No credentials are needed.
  • User Interaction: None. No victim has to click or browse anything.
  • Scope: Changed. Impact may cross the security boundary of the vulnerable component.
  • Confidentiality: High. Successful attacks can result in unauthorized access to critical data or complete access to all Oracle iStore accessible data.
  • Integrity and Availability: None. The published assessment assigns no write or denial-of-service impact.

This is a data exposure issue. Nothing in the record describes remote code execution, and we would caution against reading the score as implying it.

Root cause: not publicly documented

The public record stops at the component and the attack conditions. It does not disclose a vulnerable endpoint, parameter, request structure, payload, exploit chain or the underlying implementation defect. Oracle EBS is closed source, so there is no public commit or diff showing how the Shopping Cart code changed.

The official CVE record carries no CWE classification, and the Oracle advisory does not name one either. VulDB lists CWE 285 but marks it as unconfirmed, which is not the same as an established root cause. Given this, we cannot responsibly classify the bug as SQL injection, insecure deserialization or any particular authorization bypass, and we have not attempted to.

Why the scope change matters

FIRST's CVSS 3.1 specification defines a changed scope as impact that reaches beyond the security authority of the vulnerable component. For iStore, that fits its role as a front end tightly integrated with order processing, pricing, inventory, financials and payment authorization. Oracle explicitly warns that attacks may significantly impact additional products, but it does not name them. The scope rating is a reason to treat the exposure as larger than the storefront, but it is not evidence that every integrated EBS module or database is exposed.

Attack flow, as far as the record supports it

  1. An attacker locates a network-reachable Oracle iStore instance running an affected release between 12.2.3 and 12.2.15.
  2. Without authenticating, the attacker sends HTTP requests that reach the vulnerable Shopping Cart functionality. No user interaction is required.
  3. Because Oracle rates attack complexity as Low, no special conditions such as race windows or nondefault configuration are indicated.
  4. A successful attack yields read access to critical data or to all data accessible to iStore, and per the changed scope may affect data belonging to additional products.

The specific requests involved in step 2 have not been published, and no verified exploit is available.

A note on record status

The CVE Program record confirms publication on November 17, 2026, with Oracle as the CNA. When the source briefing was compiled, the NVD page for this identifier returned "CVE ID Not Found", so the NVD timestamp could not be independently confirmed. That gap does not affect the Oracle advisory entry or the CVE record itself.

Patch information

Oracle fixed CVE-2026-114876 in its November 2026 Critical Security Patch Update (CSPU), released on 17 November 2026. The CVE record, submitted by Oracle as the CNA, links directly to this advisory, which makes the CSPU the official fix.

What the advisory lists. The E Business Suite risk matrix entry for Oracle iStore shows:

  • Component: Shopping Cart
  • Protocol: HTTP
  • Remotely exploitable without authentication: Yes
  • CVSS 3.1 score: 8.6, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
  • Affected releases: 12.2.3 through 12.2.15

No public commit, diff or source change exists, and neither the advisory nor NVD names a CWE.

How to get the patch. Oracle does not publish a single downloadable patch number per EBS CVE. The advisory points customers to Oracle E Business Suite Release 12 Critical Security Patch Update Knowledge Document (November 2026), which is My Oracle Support Note KA923. That note determines which patches a system needs based on:

  • the EBS 12.2.x release level in use (12.2.3 to 12.2.15)
  • the code levels and patches already applied

KA923 is only available on My Oracle Support, and an active Oracle support contract is required to see the exact patch IDs and download them. The advisory describes the fix publicly, but the patch files are not freely available.

How CSPUs relate to quarterly CPUs. This fix shipped in a CSPU, not a quarterly Critical Patch Update (CPU). Oracle describes CSPUs as smaller, targeted bundles of high-priority security fixes intended to be applied with minimal disruption, and they complement the cumulative quarterly CPUs rather than replacing them. In practice:

  • Teams patching on the quarterly CPU schedule should not wait for the next CPU. Apply the November 2026 CSPU fixes from KA923 now.
  • The CSPU sits on top of your existing CPU baseline, and KA923 tells you what must already be in place.

Database and Fusion Middleware tiers. EBS includes Oracle Database and Oracle Fusion Middleware components whose fixes appear in their own sections of the advisory, not in the EBS matrix. Oracle recommends applying the November 2026 CSPU to those layers as well. For a complete fix, patch the iStore application tier using KA923 and update the underlying Database and Fusion Middleware tiers.

Interim measures. Oracle states generally that blocking network protocols required by an attack may reduce risk until patches are applied, but warns that this can break application functionality, should be tested on nonproduction systems and does not correct the vulnerability. No CVE-specific firewall rule or endpoint block has been published. Oracle's privilege removal guidance does not apply here, since the attack requires no privileges.

Affected systems and versions

  • Product: Oracle iStore, part of Oracle E Business Suite
  • Component: Shopping Cart
  • Affected supported releases: 12.2.3 through 12.2.15
  • Vulnerable configuration: any affected release where the iStore Shopping Cart is reachable over HTTP by an attacker, with no authentication or user interaction required
  • Related tiers: Oracle recommends applying the November 2026 CSPU to the Oracle Database and Oracle Fusion Middleware components of the EBS installation, although the advisory does not identify them as the root cause of this flaw

The affected range does not by itself tell you what the next safe version is. KA923 defines the required patch set for each environment.

Vendor security history

Oracle runs quarterly cumulative CPUs alongside monthly CSPUs for focused, priority fixes, and its published policy reserves the option to release exceptional patches or workaround instructions for particularly critical issues or active exploitation.

The most relevant prior EBS event is CVE-2025-61882, a flaw in the BI Publisher Integration component that could permit remote code execution. Google Threat Intelligence Group and Mandiant began tracking a large extortion campaign on September 29, 2025, in which executives received emails from an actor claiming affiliation with the CL0P brand and alleging theft of EBS data. Google assessed that attackers exploited what may have been CVE-2025-61882 as early as August 9, 2025, with suspicious activity dating to July 10, 2025, and Oracle shipped emergency patches on October 4, 2025. GTIG did not formally attribute the activity to a tracked group.

That incident involved a different component, a different identifier and a different impact class. It shows that attackers are interested in EBS data, but it should not be read as attribution or evidence of exploitation for CVE-2026-114876. For the iStore flaw, active exploitation is not confirmed in the sources we reviewed. VulDB reports "KEV: no" and "Activities: very low", and no CISA KEV entry was established for this identifier. Oracle has also noted that some successful attacks against its products used vulnerabilities whose patches were already available but had not been applied, which is the more relevant lesson for this fix.

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