Automated Threat Modeling

Quick Look: CVE-2026-114881, Unauthenticated Data Exposure and Denial of Service in Oracle EBS Document Management and Collaboration Attachments

A brief summary of CVE-2026-114881, a CVSS 9.1 flaw in the Attachments component of Oracle EBS Document Management and Collaboration (12.2.3 through 12.2.15) that lets unauthenticated HTTP attackers read application data and cause a complete denial of service. Includes Oracle's November 2026 patch guidance.

CVE Analysis

8 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-17

Quick Look: CVE-2026-114881, Unauthenticated Data Exposure and Denial of Service in Oracle EBS Document Management and Collaboration Attachments

Introduction

Oracle's November 2026 Critical Security Patch Update fixes a flaw that lets anyone with HTTP access to an affected Oracle EBS deployment, with no account and no user interaction, read critical data held by the Document Management and Collaboration product and repeatedly hang or crash it. Because EBS sits underneath order management, procurement, financials, and human resources processes in many organizations, Oracle rated this Attachments issue, CVE-2026-114881, at CVSS 3.1 9.1.

This post is a brief summary of what Oracle and other public sources have disclosed. Oracle has not released technical details, so we focus on what the published record establishes and where its limits are.

Technical Information

What Oracle disclosed

According to Oracle's risk matrix, the vulnerability sits in the Attachments component of Document Management and Collaboration, part of Oracle EBS. Oracle describes it as an easily exploitable vulnerability that allows an unauthenticated attacker with network access via HTTP to compromise Document Management and Collaboration. Successful attacks can result in:

  • Unauthorized access to critical data, or complete access to all data accessible to Document Management and Collaboration.
  • An unauthorized ability to cause a hang or frequently repeatable crash, meaning a complete denial of service of the product.

NVD lists the record as published on November 17, 2026, and displays Oracle's CNA score. NVD has not provided an independent assessment.

Reading the CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
  • Attack Vector: Network. Oracle identifies HTTP as the access protocol.
  • Attack Complexity: Low. Oracle calls it easily exploitable.
  • Privileges Required: None. No authentication is needed.
  • User Interaction: None. No victim action is required.
  • Scope: Unchanged.
  • Confidentiality: High. Critical data, or all data accessible to the product, may be exposed.
  • Integrity: None. No data modification impact is assigned.
  • Availability: High. A hang or repeatable crash produces complete denial of service.

With integrity rated None, the published assessment covers reading data and knocking the service over. It does not establish data modification, arbitrary code execution, or operating system compromise for this CVE.

Root cause: what is known and what is not

Oracle has not published a commit, diff, or root-cause write-up, and neither the NVD record nor Oracle's CNA record or CSAF entry lists a CWE. Oracle's policy is to analyze the vulnerabilities it fixes without disclosing that analysis, publishing risk matrices that describe exploitation conditions and impact instead.

VulDB independently labels the issue as improper authorization, mapping it to CWE-285 and CWE-266. That is a third-party classification, not an Oracle-disclosed explanation.

The combination of no required privileges, a network vector, and high confidentiality and availability impacts is consistent with missing authentication or authorization on a network-reachable attachment-handling path. On that reading, the fix most likely places that path behind proper authentication and access checks and hardens how it handles requests. This is an inference from the scoring. Oracle has not confirmed the code change.

Attack flow, as far as the disclosure supports

The public record supports only a high-level sequence:

  1. An attacker identifies an EBS deployment running an affected release (12.2.3 through 12.2.15) whose Document Management and Collaboration Attachments functionality is reachable over HTTP.
  2. Without credentials, the attacker sends requests that reach the vulnerable Attachments functionality.
  3. Depending on the requests, the result is unauthorized reading of critical or all product-accessible data, or a hang or frequently repeatable crash of the product.

Oracle does not publish a request path, HTTP method, parameter, payload, attachment format, or reproducible sequence, and VulDB reports that technical details are unknown and that no exploit is publicly available. We are not going to fill those gaps with guesses.

Do not confuse it with CVE-2026-114880

Oracle's risk matrix lists CVE-2026-114880 right alongside this issue. It affects the same Attachments component and the same releases, but it scores 9.8 and describes product takeover, including integrity impact. CVE-2026-114881 scores 9.1 with the narrower confidentiality and availability impacts described above. Track and report them as separate vulnerabilities.

A second, older comparison is CVE-2025-61882, which the UK NCSC describes as affecting the BI Publisher Integration component of Oracle Concurrent Processing, where specially crafted unauthenticated HTTP requests lead to full system compromise. Different component, different published impact.

Exploitation status

In the sources reviewed, active exploitation of CVE-2026-114881 is not publicly confirmed and no threat actor is named. No CVE-specific indicators have been disclosed, and a CISA KEV entry could not be established from the accessible catalog content. As the FIRST CVSS v3.1 specification points out, a Base Score reflects intrinsic severity, not evidence of an ongoing campaign. Equally, the absence of public reporting is not proof that private exploitation is impossible.

Patch Information

How the fix ships. Oracle fixed CVE-2026-114881 in the November 2026 Critical Security Patch Update (CSPU), released on November 17, 2026 (advisory Rev 1, initial release). The advisory does not link to a standalone patch for this CVE. Instead, it directs EBS customers to My Oracle Support Note KA923, the Oracle EBS Release 12 Critical Security Patch Update Knowledge Document (November 2026), which identifies the patches a given EBS 12.2.x code level needs and how to install them. Oracle's November CSPU blog post also points to an executive summary on My Oracle Support (Doc ID CPU433).

What the machine-readable advisory says. Oracle's CSAF file for the November 2026 CSPU contains a remediation entry for this CVE:

  • Category: vendor_fix
  • Applies to: the product ID covering the whole affected range, 12.2.3 through 12.2.15
  • Details: "Oracle customers with valid support contracts"
  • URL: https://support.oracle.com/support/?documentId=KA923

The CSAF data lists the affected range only as known_affected, with no separate fixed version. Oracle ships this fix as patches applied on top of your existing 12.2.x code level, not as a new EBS point release. In practice, version numbers alone will not tell you whether a system is fixed. You need to confirm that the November 2026 CSPU patches identified in KA923 have been applied.

Applying the patch correctly. Oracle recommends applying the November 2026 CSPU to the Oracle Database and Oracle Fusion Middleware components of an EBS installation as well, not only the EBS application tier. Oracle notes those component updates are not included in the EBS risk matrix and that exposure depends on the versions deployed. Use KA923 as the authoritative checklist for each environment, because the required patch set depends on your EBS release. Downloading the patches and reading the installation documentation both require a valid Oracle support contract.

Interim measures. Oracle's advisory gives general, not CVE-specific, guidance for the period before patching: blocking network protocols required by an attack may reduce risk, and removing unnecessary privileges or package access helps only for attacks that require them (this one requires no authentication). Oracle warns both approaches may break application functionality and should be tested on nonproduction systems first. These are not substitutes for the patch.

Affected Systems and Versions

  • Vendor: Oracle Corporation
  • Product: Oracle EBS, Document Management and Collaboration
  • Component: Attachments
  • Affected supported releases: 12.2.3 through 12.2.15
  • Fixed state: no fixed version number is published; systems are remediated once the November 2026 CSPU patches listed in My Oracle Support Note KA923 for that code level are applied
  • Related stack components: Oracle recommends applying the November 2026 CSPU to the Oracle Database and Oracle Fusion Middleware components of the EBS installation

An advisory naming EBS does not, by itself, indicate that Oracle Fusion Cloud ERP is affected.

Vendor Security History

Oracle ships fixes on a scheduled Critical Security Patch Update cadence and reserves the ability to release patches or workaround instructions outside that schedule for particularly critical vulnerabilities or reported active exploitation. The November 2026 CSPU alone contains 71 new EBS security patches, with 19 addressing vulnerabilities remotely exploitable without authentication. Those figures describe patch coverage, not incidents.

The most relevant prior case is CVE-2025-61882. Google reported an extortion campaign in which executives received messages alleging theft from their EBS environments, and in some cases Google confirmed significant data exfiltration. Google urged customers to apply Oracle's emergency patches released on October 4, 2025. Google noted overlaps with confirmed and suspected FIN11 activity but did not formally attribute the campaign to a tracked group at the time. That history shows EBS is an attractive target, but it does not establish exploitation of, or actor involvement in, CVE-2026-114881, and the 2025 emergency patches are not the fix for this issue.

Oracle also states that some successful attacks against its products occurred because customers had not applied patches that were already available.

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