Automated Threat Modeling

Brief Summary: CVE-2026-114882, an Unauthenticated Data Integrity Flaw in Oracle Product Workbench

A brief summary of CVE-2026-114882, a CVSS 7.5 flaw in the Internal Operations component of Oracle Product Workbench (Oracle EBS 12.2.3 through 12.2.15) that lets an unauthenticated attacker with HTTP access create, delete, or modify Product Workbench data. Includes Oracle's November 2026 CSPU patch information.

CVE Analysis

7 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-17

Brief Summary: CVE-2026-114882, an Unauthenticated Data Integrity Flaw in Oracle Product Workbench

Introduction

According to Oracle's November 2026 Critical Security Patch Update, an attacker who can reach an Oracle EBS instance over HTTP may be able to create, delete, or modify data managed by Oracle Product Workbench without logging in. For organizations that keep product structures and bills of material in EBS, CVE-2026-114882 is a data integrity problem that requires no credentials and no user interaction.

Product Workbench is a graphical interface within Oracle Product Hub, part of Oracle EBS, used to manage complex product information such as product structures, bills of material, and structured attributes. Oracle states that thousands of organizations worldwide rely on EBS for key business operations spanning financial management, human capital management, procurement, supply chain management, and customer relationship management. Product Workbench is where users create, edit, compare, copy, and import structures and review changes through redlining and markup, so integrity, not confidentiality, is the meaningful security concern for this product.

Technical information

What Oracle disclosed

The vulnerability sits in the Internal Operations component of Oracle Product Workbench. Oracle identifies supported versions 12.2.3 through 12.2.15 as affected. The CVE record was published on 17 November 2026 with a CVSS 3.1 base score of 7.5. The full vector is:

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
MetricValueMeaning
Attack vectorAV:NNetwork access (HTTP)
Attack complexityAC:LLow complexity
Privileges requiredPR:NNone
User interactionUI:NNone
ScopeS:UUnchanged
ConfidentialityC:NNo impact scored
IntegrityI:HHigh impact
AvailabilityA:NNo impact scored

Reaching the vulnerable functionality is easy: it needs no authentication, has low complexity, and is network reachable. The documented consequence is narrower, limited to unauthorized creation, deletion, or modification of critical data or all data accessible to Product Workbench.

Root cause

Oracle has not published a root cause, and since EBS is closed source there is no public commit or diff to study. The Oracle CVE record and NVD provide no CWE assignment. VulDB independently labels the issue CWE-285, Improper Authorization. Treat this as a secondary classification rather than an official root cause.

Oracle's CSAF record ties the CVE to internal Oracle Bug ID 39389291. Given that the impact is entirely on integrity and requires no authentication, the fix most likely adds a missing authentication or authorization check in front of an HTTP path that modifies data in Internal Operations. Oracle has not confirmed this, and no public code shows how the fix works.

Attack flow, as far as the public record allows

The disclosure establishes prerequisites and impact, not an implementation. Based on the published vector and description:

  1. The attacker needs network reachability to the EBS HTTP interface serving Product Workbench.
  2. No account, privileges, or victim interaction are required (PR:N, UI:N), and Oracle describes the issue as easily exploitable (AC:L).
  3. The attacker sends HTTP requests to the vulnerable Internal Operations functionality. Oracle has not disclosed the specific URL, HTTP method, parameter, request body, or payload.
  4. A successful attack yields unauthorized creation, deletion, or modification access to critical data or all data accessible to Product Workbench, within an unchanged security scope.

The evidence does not establish remote code execution, database takeover, confidentiality loss, or service disruption. We have not reconstructed a request sequence because no public source supports one.

Exploitation status

The reviewed sources do not confirm active exploitation or identify a threat actor. VulDB states that technical details are unknown and that no exploit is available. The CVE was not present in the retrieved CISA Known Exploited Vulnerabilities catalog (version 2026.11.17). None of this proves that exploitation has not occurred. It describes the current state of public information.

Patch information

Oracle fixed CVE-2026-114882 in its November 2026 Critical Security Patch Update (CSPU), published on 17 November 2026.

What Oracle published

  • Risk matrix entry: The EBS risk matrix lists the CVE as Product Workbench / Internal Operations, protocol HTTP, remotely exploitable without authentication, CVSS 3.1 base score 7.5, affected versions 12.2.3 through 12.2.15.
  • CSAF record: Oracle's machine-readable CSAF file (cspunov2026csaf.json) ties the CVE to internal Oracle Bug ID 39389291, covers the Product Workbench 12.2.3 through 12.2.15 product entry, and lists a vendor_fix remediation pointing to My Oracle Support document KA923.

Getting and applying the fix

EBS fixes are delivered through a chain of support documents that require an Oracle support contract:

  1. MOS KA923, Identifying the Latest Monthly and Quarterly Critical Patch Update for Oracle E Business Suite Release 12.2: the entry point referenced by the CSAF remediation.
  2. MOS KA1855, Oracle E Business Suite Release 12.2 Critical Security Patch Update Availability Document (November 2026): lists the exact patch numbers for each EBS code level.
  3. EBS Critical Patch Update Checker (ECPUC), shipped as Patch 35583866 and updated for the November 2026 CSPU. Running ECPUC.sql produces an ECPUC.lst report showing your current CSPU/CPU level and every required patch and security fix. Oracle advises running it before patching to see what you need, then again after patching and cutover to confirm everything applied. Always use the latest ECPUC version, because older versions do not check for newer fixes.

Things to watch when patching

  • Patch the whole stack: The EBS risk matrix does not list Database or Fusion Middleware fixes, but Oracle tells customers to also apply the November 2026 CSPU to the Oracle Database and Fusion Middleware components inside EBS. Your actual exposure depends on those versions too. This is broader patch program guidance, not evidence that CVE-2026-114882 itself resides in those layers.
  • Test first: Oracle recommends applying patches to systems outside production before production.
  • Do not rely on NVD yet: NVD had not finished ingesting this CVE when checks ran, so its record may be incomplete. Use Oracle's advisory and CSAF data as the reference.

Interim measures

Oracle states that blocking network protocols required by an attack may reduce risk until patches are applied. HTTP is the protocol identified for this CVE. No specific endpoint rule or WAF signature has been published. Oracle's general advice to remove unnecessary privileges applies only to attacks that require those privileges, so it is not an established mitigation for this unauthenticated issue. Both workarounds may break functionality, need testing, and do not fix the underlying vulnerability.

Affected systems and versions

  • Vendor: Oracle Corporation
  • Product: Oracle Product Workbench, part of Oracle EBS
  • Component: Internal Operations
  • Affected supported versions: 12.2.3 through 12.2.15, inclusive
  • Vulnerable configuration: any affected deployment whose Product Workbench HTTP interface is reachable by an attacker, with no authentication or user interaction required
  • Related layers: Oracle advises that exposure in an EBS deployment also depends on installed Oracle Database and Fusion Middleware versions, which have their own November 2026 CSPU fixes

Vendor security history

Oracle's November 2026 CSPU contains 71 new security patches for Oracle EBS, and Oracle states that 19 of those vulnerabilities may be remotely exploitable without authentication. These figures describe remediation scope, not attacks.

Oracle also says it periodically receives reports of attempts to exploit vulnerabilities for which patches already exist, including successful attacks against customers that had not applied available patches. Oracle recommends staying on supported versions and patching without delay.

For context, Google Threat Intelligence Group documented a widespread extortion campaign involving CVE-2025-61882, a different Oracle EBS vulnerability. Oracle directed customers to apply emergency patches on October 4, 2025, and Google reported significant data exfiltration from some affected organizations. Google did not formally attribute that activity to a tracked group and cautioned that CL0P branding had not been used exclusively by FIN11. That campaign does not establish exploitation of CVE-2026-114882, whose published vector scores integrity impact only.

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