Automated Threat Modeling

Quick Look: Oracle Sales Online CVE-2026-114871, an Authenticated Data Access and Modification Flaw in Oracle EBS

A brief summary of CVE-2026-114871, a CVSS 8.1 flaw in the Internal Operations component of Oracle Sales Online that lets a low-privileged user with HTTP access read and modify application data, along with Oracle's November 2026 patch guidance.

CVE Analysis

7 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-17

Quick Look: Oracle Sales Online CVE-2026-114871, an Authenticated Data Access and Modification Flaw in Oracle EBS

Introduction

A newly patched flaw in Oracle Sales Online lets an attacker who holds only a low-privileged account read, create, modify or delete critical application data, using nothing more than network access over HTTP. For organizations running Sales Online on Oracle EBS releases 12.2.3 through 12.2.15, CVE-2026-114871 (CVSS 8.1) is a data confidentiality and integrity issue that Oracle addressed in its November 2026 Critical Security Patch Update.

Oracle Sales Online is a product within Oracle E Business Suite (EBS), Oracle's long-running ERP application suite. For context on scale, APPS RUN THE WORLD estimates that Oracle ranked first in the worldwide ERP applications market in 2024 with 6.63% share, narrowly ahead of SAP at 6.57%. These are portfolio-level estimates, not Sales Online figures. EBS also sits on top of Oracle Database and Oracle Fusion Middleware, so patching decisions for one module tend to touch the wider stack.

Technical Information

What Oracle disclosed

Oracle's November 2026 risk matrix places the issue in Oracle Sales Online, component Internal Operations, reachable over HTTP. Oracle marks it as not remotely exploitable without authentication, since the attacker needs low privileges. The published vector is:

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

Reading the vector against the FIRST CVSS 3.1 definitions:

  • Attack Vector, Network (AV:N): access over HTTP is sufficient.
  • Attack Complexity, Low (AC:L): no special conditions are needed beyond the stated prerequisites.
  • Privileges Required, Low (PR:L): this is an authenticated attack, not an anonymous one.
  • User Interaction, None (UI:N): no other user has to click or act.
  • Scope, Unchanged (S:U): impact stays within the same security authority.
  • Confidentiality, High (C:H): unauthorized access to critical data or complete access to all Sales Online accessible data.
  • Integrity, High (I:H): unauthorized creation, deletion or modification of critical data or all Sales Online accessible data.
  • Availability, None (A:N): no availability impact is assigned.

Low complexity does not remove the low-privilege prerequisite, and the disclosed data impact is not a statement of operating system takeover.

Root cause: what is and is not known

Oracle Sales Online is closed source, so there is no public commit, diff or changelog. Oracle has not disclosed an affected URL, vulnerable parameter, request format, payload, exploit chain or underlying coding error, and nothing in the record describes code execution.

No CWE is assigned in the NVD or CVE.org record. VulDB displays CWE-285, but explicitly labels that classification as unconfirmed, so it should not be read as Oracle's root cause.

The impact profile is consistent with a server-side authorization or access control weakness in the Internal Operations component. A low-privileged user reaches and alters data well beyond what that role should touch, with no availability effect. The fix probably adds or tightens checks there. Treat that as an inference from the published metrics, not a documented fact.

Attack flow supported by the public record

  1. The attacker holds a low-privileged account on the target EBS instance (PR:L).
  2. The attacker reaches Oracle Sales Online over the network via HTTP (AV:N).
  3. The attacker interacts with functionality in the Internal Operations component. No special conditions and no action by another user are required (AC:L, UI:N).
  4. The result is unauthorized read access to critical or all Sales Online accessible data, plus the ability to create, delete or modify that data (C:H, I:H), without impact to availability or to other security authorities (A:N, S:U).

The specific requests, endpoints and data objects involved remain undisclosed in the primary records we reviewed.

Exploitation status

Active exploitation of CVE-2026-114871 is not publicly confirmed in the sources we reviewed. The Oracle, CVE and NVD records name no campaign, victim, threat actor or malware family, and we found no public proof of concept or CVE-specific indicators. CISA KEV inclusion could not be conclusively established from the catalog content available to us. VulDB shows a negative KEV flag, but that secondary flag is not a definitive CISA finding. None of this proves exploitation has not occurred, only that public information is limited.

Patch Information

Oracle fixed CVE-2026-114871 in its November 2026 Critical Security Patch Update (CSPU), released on 17 November 2026 (advisory cspunov2026, Rev 1). Everything known about the fix comes from Oracle's advisory and its risk matrices.

What the advisory confirms. The CVE appears in the Oracle EBS risk matrix with these details:

  • Product and component: Oracle Sales Online (EBS), Internal Operations
  • Protocol: HTTP
  • Remotely exploitable without auth: No (low privileges required)
  • CVSS 3.1: 8.1, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
  • Supported versions affected: 12.2.3 through 12.2.15

Oracle's risk matrices list only vulnerabilities newly addressed by the patches in that advisory. Because this CVE is listed, the November 2026 EBS patch set is the first one that fixes it.

How the fix is delivered. Oracle does not ship EBS fixes as a new product version, so no single newer release fixes this CVE. Instead, Oracle releases patches applied on top of your existing 12.2.x code line. This CSPU includes 71 new security patches for Oracle EBS, and the Sales Online fix is one of them. To determine which patches your installation needs, Oracle refers customers to the Oracle E Business Suite Release 12 Critical Security Patch Update Knowledge Document (November 2026), My Oracle Support Note KA923. Patch numbers and downloads require a valid support contract, and the public sources we reviewed do not give a specific patch ID for this CVE.

Applying it correctly:

  • Patch the EBS application tier using KA923. This is the only change that actually fixes CVE-2026-114871.
  • Update the underlying stack too. EBS runs on Oracle Database and Oracle Fusion Middleware, and fixes for those components are not listed in the EBS matrix. Oracle recommends applying the November 2026 CSPU to them as well. This does not fix this CVE, but it closes related exposure in the same deployment.
  • Check your version. The matrix covers only supported versions 12.2.3 through 12.2.15. Older or out-of-support releases may never get a fix, and Oracle's guidance is to stay on actively supported versions.
  • Test before production. Oracle advises validating CSPU changes on nonproduction systems first.

Interim measures Oracle documents. Oracle's advisory notes that blocking network protocols required by an attack, or removing privileges or package access that users do not need, may reduce risk until patching. Oracle also warns that both can break application functionality and neither corrects the underlying problem. These are general advisory recommendations, not validated workarounds for this specific CVE, and no CVE-specific WAF rule or configuration recipe has been published.

Verification gap. NVD had not yet loaded the record when we checked the patch details. Oracle's advisory and the text-form risk matrix are the authoritative public evidence that a fix exists.

Affected Systems and Versions

  • Product: Oracle Sales Online, part of Oracle EBS
  • Component: Internal Operations
  • Affected supported versions: 12.2.3 through 12.2.15
  • Vulnerable configuration: Sales Online reachable over HTTP by an attacker holding a low-privileged account
  • Unsupported releases: not covered by the risk matrix, and Oracle's policy is that unsupported versions do not receive fixes
  • Fixed state: defined by applying the November 2026 EBS CSPU patches listed in KA923, not by a version number

Vendor Security History

Oracle's published process includes quarterly Critical Patch Updates, complementary targeted Critical Security Patch Updates, and out-of-schedule Security Alerts for urgent issues. Security updates are available to active Oracle Support customers, and unsupported product versions do not receive fixes.

The most relevant recent precedent is CVE-2025-61882, a separate 2025 EBS vulnerability. The UK NCSC described it as an unauthenticated vulnerability in BI Publisher Integration that could lead to full system compromise. Google Threat Intelligence reported that attackers exfiltrated significant data from some affected organizations and sent executives extortion emails alleging theft from EBS environments. Google also recorded that Oracle initially advised applying July 2025 patches on 2 October 2025, then directed customers to emergency patches on 4 October 2025 for the newly identified vulnerability.

Google noted overlaps with confirmed and suspected FIN11 activity for that campaign while stating it had not formally attributed the activity to a tracked group. That observation does not carry over to CVE-2026-114871. The 2025 issue was unauthenticated and affected a different component, whereas this one requires low privileges and is limited to Sales Online data confidentiality and integrity.

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