Automated Threat Modeling

Brief Summary: CVE-2026-91551, Unauthenticated Information Disclosure in Oracle Platform Security for Java

CVE-2026-91551 is a CVSS 7.5 unauthenticated HTTP information disclosure flaw in the Centralized Thirdparty Jars component of Oracle Platform Security for Java 12.2.1.4.0 and 14.1.2.0.0. This summary covers what Oracle has disclosed, the patch in the November 2026 CSPU, and the current exploitation status.

CVE Analysis

7 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-17

Brief Summary: CVE-2026-91551, Unauthenticated Information Disclosure in Oracle Platform Security for Java

Introduction

An attacker who can reach an affected Oracle Fusion Middleware deployment over HTTP may be able to read critical data, or potentially all data accessible to Oracle Platform Security for Java, without credentials and without any user interaction. Oracle fixed the issue, tracked as CVE-2026-91551, in its November 2026 Critical Security Patch Update. Because the flaw lives in a shared library component, the fix is relevant to more than a single application.

Oracle Platform Security for Java, also known as Oracle Platform Security Services (OPSS), is a standards-based security framework for Java SE and Java EE applications. It supplies security, identity management and audit services. Oracle says OPSS underlies Fusion Middleware products including WebLogic Server, SOA, WebCenter, ADF and OES. Fusion Middleware is Oracle's product family for application development, integration, identity management, collaboration and business intelligence reporting, used by small, midsize and enterprise organizations.

Technical information

What Oracle has disclosed

Oracle, acting as the CNA, describes the issue as a vulnerability in the Oracle Platform Security for Java product of Oracle Fusion Middleware, component Centralized Thirdparty Jars. According to the description, it is easily exploitable and allows an unauthenticated attacker with network access via HTTP to compromise OPSS. Successful attacks can result in unauthorized access to critical data or complete access to all OPSS-accessible data.

  • CVSS 3.1 base score: 7.5 (High), supplied by Oracle. NVD does not present a separate assessment.
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
  • NVD publication: November 17, 2026, record status Received, source [email protected].
  • CWE: none assigned in the Oracle CNA or NVD records.

Reading the vector

MetricValueWhat it means
Attack VectorNetworkExploitation is possible through network access. The description specifies HTTP.
Attack ComplexityLowNo special conditions are scored as required.
Privileges RequiredNoneNo account is needed.
User InteractionNoneNo victim needs to click, open or visit anything.
ScopeUnchangedNo impact is scored beyond the vulnerable component's security scope.
ConfidentialityHighCritical information, or potentially all information accessible to OPSS, may be disclosed.
Integrity and AvailabilityNoneThe published assessment does not support claims of data modification, service disruption or code execution.

This is a confidentiality-focused issue with an unauthenticated, network-reachable entry point. The High rating comes from that combination. Nothing in the score rests on a claim of remote code execution.

Root cause: what is and is not known

Oracle ships closed-source binary patches, and there is no public commit, diff or source change for this CVE. The advisory's notes column for this row is blank. Oracle has not identified the specific third-party library, JAR filename, vulnerable method, HTTP endpoint, request structure or payload involved.

Secondary sources classify the flaw differently. VulDB labels it improper authorization and lists CWE-285 / CWE-266, while TheHackerWire calls it an authentication bypass. These are third-party classifications. Neither is a vendor-confirmed explanation of the vulnerable code path.

Why the component name matters

In Fusion Middleware, "Centralized Thirdparty Jars" refers to the shared set of open source libraries that many FMW products load from one common location in the Oracle Home. Fixes for this component usually work by replacing or upgrading those JARs, so one patch protects every product in that Oracle Home that loads the shared library, not just OPSS. This explains why the fix is listed under OPSS rather than under a single end-user product.

That is general background on how the component works, and it is not a confirmed description of what this particular patch changes. It also does not establish that every product using OPSS is exploitable through this CVE. Oracle's disclosure names the affected product and releases, not a full map of deployment exposure.

Attack flow

Based only on what Oracle has published, the attack prerequisites and outcome look like this:

  1. The attacker has network access to an HTTP interface of an affected Oracle Platform Security for Java deployment (12.2.1.4.0 or 14.1.2.0.0).
  2. The attacker interacts with the target over HTTP without supplying credentials and without needing any user to take an action.
  3. A successful attack exposes critical data, or potentially all data accessible to OPSS, to the attacker.

The specific requests, endpoints and payloads that achieve step 2 have not been disclosed, and we have not attempted to reconstruct them.

Exploitation status

As of November 18, 2026, active exploitation is not confirmed. We found no matching entry in the CISA Known Exploited Vulnerabilities catalog we reviewed, and TheHackerWire also reports it is not listed. VulDB reports no exploit available, TheHackerWire says no public exploit code has been confirmed, and Infrastack (last reviewed November 17) reports no exploitation or proof of concept found.

No threat actor attribution or CVE-specific indicators of compromise have been established, and the EPSS score was still computing at the time of review. These findings describe visibility at one point in time. They do not prove exploitation has never occurred.

Patch information

Oracle fixed CVE-2026-91551 in its November 2026 Critical Security Patch Update (CSPU), released on November 17, 2026. The fix covers both supported release lines Oracle lists as affected, 12.2.1.4.0 and 14.1.2.0.0.

Where to get the patch

  • The Fusion Middleware row in the advisory's Patch Availability table links to My Oracle Support document CPU450, which maps each affected release to its patch number and installation instructions.
  • Downloading patch binaries requires a valid Oracle support contract. The advisory and its risk matrices are public.
  • The OPSS section of the same CSPU also lists CVE-2026-91548, CVE-2026-91560 and CVE-2026-114824. Applying the OPSS / Fusion Middleware patches from this release, rather than picking out a single fix, addresses all of them together. This CSPU contains 71 new Fusion Middleware security patches in total.

How CSPUs relate to quarterly CPUs

Oracle describes CSPUs as smaller, targeted, high-priority security fixes that complement its quarterly cumulative Critical Patch Updates. Two practical consequences follow:

  1. This fix arrived between CPU cycles, so the October 2026 CPU does not include it. A system fully current on that CPU is still exposed until the November CSPU content is applied.
  2. CSPUs are meant to be faster to deploy than a full CPU. The fix is expected to be included in later cumulative CPUs, so plan your patch baseline around that.

Versions outside support

Oracle only tests releases under Premier or Extended Support. It says earlier versions are "likely" affected as well and does not provide patches for them. The supported path for those installations is to upgrade to 12.2.1.4.0 or 14.1.2.0.0 and then apply the November 2026 CSPU patch.

Verifying the patch

Oracle has not published a code-level indicator for this fix. To confirm it, look up the patch numbers for your release in CPU450, then use OPatch to check that each Oracle Home lists them as applied:

opatch lspatches

Interim risk reduction

Oracle notes that blocking protocols required by an attack may reduce the risk of successful attack before patching. It also warns that such measures may break application functionality, should be tested outside production, and are not long-term solutions because they do not correct the underlying flaw. HTTP is the disclosed protocol, but no specific blocking rule or endpoint has been published. Oracle's general advice about removing unnecessary privileges is not a sufficient mitigation here, since the vulnerability requires no privileges.

Affected systems and versions

  • Product: Oracle Platform Security for Java (OPSS), Oracle Fusion Middleware
  • Component: Centralized Thirdparty Jars
  • Supported affected versions: 12.2.1.4.0 and 14.1.2.0.0
  • Vulnerable configuration: any affected installation an attacker can reach over HTTP. No authentication or user interaction is required.
  • Not fixed by: the October 2026 CPU alone. The November 2026 CSPU content is required.
  • Unsupported releases: Oracle states earlier versions are likely affected and does not patch them. An older installation missing from the supported affected version list is not safe for that reason.
  • Shared library consideration: because Centralized Thirdparty Jars are loaded from a common location in the Oracle Home, review every Oracle Home in your estate that contains the affected release, not only those you think of as OPSS deployments.

Vendor security history

Oracle maintains a Software Security Assurance program covering product design, development, testing and maintenance, with secure coding standards, mandatory security training, security leaders within development groups and automated analysis and testing. It publishes quarterly Critical Patch Updates and, between those cycles, targeted Critical Security Patch Updates. Oracle has also stated that it receives attempts to exploit vulnerabilities it has already patched, and that some succeed because customers have not applied available updates.

Oracle middleware has a documented exploitation history. It is useful context, but it does not transfer to this CVE:

  • CVE-2021-35587 (Oracle Access Manager, OpenSSO component): Belgium's Centre for Cybersecurity reported active exploitation of this unauthenticated HTTP flaw, which permitted account creation with arbitrary privileges or code execution.
  • CVE-2025-61882 (Oracle E Business Suite, Concurrent Processing and BI Publisher Integration): Oracle issued a dedicated alert describing unauthenticated remote exploitation that may result in code execution, scored 9.8, and published observed compromise indicators.

Both cases share an unauthenticated HTTP access path with CVE-2026-91551, but they involve different components, different impacts and different evidence of exploitation. CVE-2026-91551 has a confidentiality-only impact profile and no confirmed exploitation, and the indicators and attribution from those incidents should not be applied to it.

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