Automated Threat Modeling

Brief Summary: Oracle Collaborative Planning CVE-2026-114896, an Authenticated Horizontal View Flaw Leading to Module Takeover

A brief summary of CVE-2026-114896, an authenticated HTTP flaw in the Horizontal View component of Oracle Collaborative Planning (Oracle EBS 12.2.3 through 12.2.15) that can lead to takeover of the module. We cover the published technical details, Oracle's November 2026 CSPU patch guidance and the affected versions.

CVE Analysis

7 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-17

Brief Summary: Oracle Collaborative Planning CVE-2026-114896, an Authenticated Horizontal View Flaw Leading to Module Takeover

Introduction

A newly patched flaw in the Horizontal View component of Oracle Collaborative Planning lets an authenticated user holding only low privileges take over the Collaborative Planning application over HTTP. Horizontal View is where planners view and edit supply and demand data, including sales forecasts, order forecasts, supply commitments and negotiated capacity. The affected code therefore sits directly inside supply chain planning workflows, not in a peripheral utility.

Oracle Collaborative Planning is a module of Oracle EBS, Oracle's enterprise application suite spanning customer relationship management, financial management, human capital management, procurement, supply chain management and other business areas. Within the module, Horizontal View displays supply and demand information over time, can aggregate supplies and demands, and supports editing several planning order types. The sources we reviewed give no customer count or deployment share for Collaborative Planning, so we make no claim about how many installations are exposed. Oracle's broader recognition in enterprise applications (Oracle Fusion Cloud ERP was named a Leader in two 2025 Gartner Magic Quadrant reports for Cloud ERP) concerns a different product line.

Technical information

What Oracle has published

Oracle, acting as the CNA, and NVD describe the issue in the same terms: a vulnerability in Oracle Collaborative Planning (component: Horizontal View), affecting supported versions 12.2.3 through 12.2.15, that is easily exploitable by a low-privileged attacker with network access via HTTP and that can result in takeover of Oracle Collaborative Planning. The CVSS 3.1 base score is 8.8, which NVD rates High (not Critical).

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

Reading the vector metric by metric:

  • AV:N (Attack Vector: Network): reachable remotely. Oracle's risk matrix lists the protocol as HTTP.
  • AC:L (Attack Complexity: Low): no special conditions are required.
  • PR:L (Privileges Required: Low): the attacker needs an authenticated, low-privileged account. Oracle's matrix marks it as not remotely exploitable without authentication.
  • UI:N (User Interaction: None): no victim action is needed.
  • S:U (Scope: Unchanged): the impact is scored within the vulnerable component's own security authority.
  • C:H / I:H / A:H: high impact to confidentiality, integrity and availability of Oracle Collaborative Planning.

The privilege requirement narrows who can attack. Combined with low complexity and no user interaction, though, it should not be read as a sign that exploitation is difficult.

Root cause

Oracle has not published the root cause. The NVD weakness enumeration has no populated CWE entry, and the CNA record provides no weakness classification. VulDB separately assigns CWE-269, placing the issue in the privilege management weakness class, but this is a third-party classification and not an Oracle explanation of the defect. VulDB itself states that technical details are unknown.

This is a proprietary, closed-source product, so there is no public commit, diff or code snippet showing what changed in Horizontal View. The public record does not identify a vulnerable endpoint, request parameter, payload, function or request sequence. It also does not establish arbitrary operating system command execution, SQL injection, or takeover of every EBS component. The confirmed outcome is potential takeover of Oracle Collaborative Planning by a low-privileged authenticated user.

Attack flow, as far as the record supports it

Working only from Oracle's description and the CVSS vector, the attack path looks like this:

  1. The attacker holds a valid low-privileged account on an affected Oracle EBS instance with Collaborative Planning (PR:L).
  2. The attacker has network reach to the EBS HTTP interface (AV:N, protocol HTTP).
  3. The attacker interacts with Horizontal View functionality. No victim interaction (UI:N) and no special environmental conditions (AC:L) are required.
  4. Successful exploitation results in takeover of Oracle Collaborative Planning, with high impact to confidentiality, integrity and availability.

We deliberately stop there. Oracle does not distribute exploit or proof-of-concept code, and no public source describes the request sequence, so any more specific description would be speculation.

Why the component matters

Oracle's Collaborative Planning guide describes Horizontal View as the place where supply and demand information is displayed over time and where order types such as sales forecasts, order forecasts, supply commitments and negotiated capacity can be edited. That helps identify which application owners and planning teams should be involved in remediation. The vulnerability record, however, does not specify which individual planning records an attacker could access or modify. The confirmed impact remains takeover of the Collaborative Planning module.

Exploitation status

In the material we reviewed, active exploitation is not publicly confirmed and no threat actor is attributed. VulDB reports that no exploit is available. That reflects public visibility only and does not prove that no private exploit exists. The accessible CISA Known Exploited Vulnerabilities catalog view did not return a conclusive CVE-specific result, so we cannot state either way whether CISA lists it. No indicators of compromise, file hashes, attacker infrastructure or detection signatures have been published for this CVE.

Patch information

Oracle fixed CVE-2026-114896 in its November 2026 Critical Security Patch Update (CSPU), released on 17 November 2026 (Rev 1, initial release). Oracle lists it in the E Business Suite risk matrix of the advisory, which Oracle describes as a table of fixed vulnerabilities. According to Oracle, the fix closes the path by which an authenticated low-privileged user with HTTP access could take over Oracle Collaborative Planning.

Finding the actual patch

Oracle's public pages do not name the Collaborative Planning patch number. The path to it is:

  1. Advisory to patch document. The Patch Availability Document column for EBS in the advisory points to My Oracle Support (MOS) note KA923, Identifying the Latest Monthly and Quarterly Critical Patch Update for Oracle E Business Suite Release 12.2.
  2. November-specific availability document. Oracle's EBS Technology blog names MOS note KA1855, Oracle E Business Suite Release 12.2 Critical Security Patch Update Availability Document (November 2026). This lists patch numbers per product, including Collaborative Planning, and requires a MOS login.
  3. Underlying stack. Oracle also recommends applying the November 2026 CSPU to the Oracle Database and Oracle Fusion Middleware components bundled with EBS. Those tiers have their own advisory entries, separate from this application-tier fix, and Oracle notes they are not listed in the EBS risk matrix.

Verifying installation with ECPUC

Oracle updated the EBS Critical Patch Update Checker (ECPUC), delivered as Patch 35583866, to cover the November 2026 CSPU. It provides the script ECPUC.sql, which writes an ECPUC.lst report showing the environment's current CSPU/CPU level and listing any required security patches still missing. Oracle's guidance:

  • Use the latest ECPUC. Older versions do not check for newly released fixes, so an outdated copy will not flag this CVE.
  • Run it before patching to see which fixes the environment needs.
  • Run it again after patching and cutover (EBS 12.2 uses online patching) to confirm the fixes were applied.
  • Apply to nonproduction first, then promote to production.

Support scope and cadence

Oracle only provides CSPU patches for releases under Premier Support or Extended Support, and it does not test older releases for these vulnerabilities, so being on a supported release is part of the fix. Monthly CSPUs supplement the quarterly cumulative CPUs, and Oracle says to apply the November fixes as soon as possible. The next CSPU is due 15 December 2026, and the next quarterly CPU on 19 January 2027.

If patching is delayed

Oracle's advisory describes two general interim approaches: blocking the network protocols required by an attack, and removing privileges or package access from users who do not need them. For this CVE the prerequisites are HTTP access and low privileges, but Oracle has not published a specific firewall rule, URL filter, package restriction or configuration setting. Oracle warns that these measures can break application functionality, should be tested in nonproduction first, and do not correct the underlying vulnerability. Treat them as conditional containment, not a substitute for the patch.

To remediate, apply the Collaborative Planning patch listed in MOS KA1855, patch the bundled Database and Fusion Middleware tiers, and run the latest ECPUC to confirm both.

Affected systems and versions

  • Vendor: Oracle Corporation (the CVE feed lists the vendor as unknown, but the NVD and CNA records identify Oracle).
  • Product: Oracle Collaborative Planning, part of Oracle EBS.
  • Component: Horizontal View.
  • Affected supported versions: 12.2.3 through 12.2.15, inclusive.
  • Attack prerequisites: a low-privileged authenticated account and network access to the application over HTTP.
  • Unsupported releases: Oracle does not test releases outside Premier Support or Extended Support for these vulnerabilities and does not provide CSPU patches for them.

Do not assume that the newest listed release, 12.2.15, is unaffected. Use KA923, KA1855 and ECPUC output to determine the required fixes for each environment.

Vendor security history

Oracle delivers fixes through quarterly cumulative Critical Patch Updates, targeted Critical Security Patch Updates in the intervening months, and Security Alerts for issues too urgent to wait for the next scheduled update. Oracle states that it does not distribute exploit or proof-of-concept code and limits vulnerability detail to advisories, installation notes, readme files and FAQs, which explains the sparse public detail on this CVE.

The most relevant prior event is the 2025 Oracle EBS extortion campaign. Google's threat intelligence teams reported that, beginning 29 September 2025, they tracked an extortion campaign by an actor claiming affiliation with the CL0P brand, with significant data exfiltration from some affected organizations. Google discussed exploitation associated with what may have been CVE-2025-61882 while acknowledging uncertainty about the exact vulnerability and exploit chain, and Oracle issued an emergency patch on 4 October 2025. Google did not formally attribute the activity, noting overlaps with confirmed and suspected FIN11 activity but explaining that CL0P branding alone was not sufficient for attribution.

That campaign shows that Oracle EBS has been targeted for data theft in practice. It involves a different identifier and component, and it is not evidence that CL0P, FIN11 or any other actor is exploiting CVE-2026-114896.

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