Automated Threat Modeling

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

A brief summary of CVE-2026-91548, an unauthenticated HTTP vulnerability in Oracle Platform Security for Java (Centralized Thirdparty Jars) rated CVSS 8.6 with high confidentiality impact and changed scope. It covers the affected versions and how to get Oracle's fix from the November 2026 Critical Security Patch Update.

CVE Analysis

7 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-17

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

Introduction

Oracle Platform Security for Java sits underneath a wide range of Oracle Fusion Middleware applications, so a flaw in it reaches past any single application. CVE-2026-91548, fixed in Oracle's November 2026 Critical Security Patch Update, allows an unauthenticated attacker with HTTP access to read critical data available to this security layer, and Oracle explicitly warns that the impact can extend to additional products.

Oracle Platform Security for Java appears in Oracle's risk matrix under Oracle Platform Security Services (OPSS), a security framework for Java SE and Java EE applications. Oracle documents OPSS as the underlying security platform for products including WebLogic Server, SOA applications, WebCenter, Oracle ADF applications, and Oracle Entitlements Server. That shared role across the middleware stack is why a confidentiality flaw here deserves attention from anyone running Fusion Middleware 12.2.1.4.0 or 14.1.2.0.0, even though those architectural relationships do not by themselves mean each named product is independently affected.

Technical Information

What Oracle has disclosed

The vulnerability is in the Centralized Thirdparty Jars component of Oracle Platform Security for Java. Oracle rates it CVSS 3.1 8.6 (High). On the FIRST scale, High spans 7.0 to 8.9 and Critical starts at 9.0, so this is a serious issue but not a Critical one. Oracle describes it as easily exploitable by an unauthenticated attacker with network access via HTTP, resulting in unauthorized access to critical data or complete access to all data accessible to Oracle Platform Security for Java.

The published vector is:

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

Broken down:

  • AV:N: reachable over the network
  • AC:L: low attack complexity
  • PR:N: no privileges or credentials required
  • UI:N: no user interaction required
  • S:C: changed scope. Oracle states attacks may significantly impact additional products
  • C:H: high confidentiality impact
  • I:N / A:N: no integrity or availability impact assigned

The impact profile is information disclosure. Neither the description nor the vector establishes remote code execution, data modification, or service disruption, so calling this a server takeover would go beyond what Oracle has published.

HTTP includes HTTPS

Oracle's advisory notes that when a protocol is listed, its secure variant is also affected. Listing HTTP therefore puts HTTPS in scope as well. Terminating TLS in front of an affected deployment does not take it out of the attack surface.

What the component name tells us, and what it does not

In OPSS, "Centralized Thirdparty Jars" is the shared set of third-party Java libraries that the platform bundles and maintains in one place. Oracle uses this kind of component label when the vulnerable code lives in a bundled open-source library rather than in Oracle's own code, and a fix for this type of issue usually replaces or upgrades the bundled JAR(s) with a corrected upstream release.

The advisory does not say which third-party library or upstream CVE this entry corresponds to. It mentions libraries such as Log4j, Bouncy Castle, Apache HttpClient, and Jackson Databind elsewhere, but ties none of them to CVE-2026-91548. We recommend against inferring the vulnerable library from the component name.

Root cause details that remain unpublished

The primary records give the component, affected versions, attack conditions, and impact. They do not provide a vulnerable endpoint, request parameter, payload, Java class, named dependency, or reproducible exploitation sequence, and no CWE classification has been assigned. Some secondary coverage labels the issue an authentication bypass, but Oracle's description does not establish that specific mechanism. The most precise supported characterization is an easily exploitable, unauthenticated HTTP vulnerability with high confidentiality impact and changed scope.

Attack flow based on the disclosed conditions

Within the limits of what Oracle has published, the attack conditions look like this:

  1. The attacker has network access to an HTTP or HTTPS path served by an affected deployment of Oracle Platform Security for Java 12.2.1.4.0 or 14.1.2.0.0.
  2. No account, credentials, or privileges are needed, and no victim user has to take any action.
  3. The attacker exploits the flaw in the Centralized Thirdparty Jars component with low complexity.
  4. The result is unauthorized access to critical data, up to all data accessible to Oracle Platform Security for Java.
  5. Because scope is changed, the exposure may significantly affect additional products beyond OPSS itself. Oracle does not name those products in this CVE record.

The specific request or payload used in step 3 has not been disclosed, so defenders cannot currently build a reliable custom exploit test for this issue.

Exploitation status

Reviewed vulnerability trackers report no known exploitation and no public proof of concept as of November 17, 2026, and no known ransomware campaign. No threat actor is associated with this CVE. The CISA Known Exploited Vulnerabilities catalog version 2026.11.17, released November 17, 2026 at 17:53 UTC, has no entry for it. These statements only describe what had been reported at that point. Absence from a snapshot is not proof that exploitation has not occurred, and Oracle's description of easy exploitation is not itself evidence of an observed attack.

Patch Information

The fix ships in Oracle's November 2026 Critical Security Patch Update (CSPU), published November 17, 2026. CVE-2026-91548 appears in the Oracle Fusion Middleware risk matrix under Oracle Platform Security for Java (OPSS), Centralized Thirdparty Jars component. This is a closed-source vendor fix, so there is no public commit or diff. The advisory is the authoritative record of the patch.

Oracle describes the CSPU program as delivering targeted, high-priority fixes in a smaller, more focused format that complements, rather than replaces, the quarterly cumulative Critical Patch Updates.

Versions covered by the fix

  • Oracle Platform Security for Java 12.2.1.4.0 (Centralized Thirdparty Jars)
  • Oracle Platform Security for Java 14.1.2.0.0 (Centralized Thirdparty Jars)

You fix these by installing the November 2026 patch on top of each release line. Oracle has not published a separate fixed version number for this CVE.

Obtaining and confirming the patch

  • Oracle directs Fusion Middleware customers to the Patch Availability Document for Fusion Middleware, My Oracle Support Note CPU450, which lists the exact patch numbers for OPSS 12.2.1.4.0 and 14.1.2.0.0 and links to installation instructions.
  • Downloads require a valid Oracle support contract. Patch numbers are not public. They are listed in the MOS note.
  • Read the patch readme and inventory to see which bundled third-party JARs were replaced. That is the most reliable way to confirm the vulnerable library is gone after patching. Replacing an arbitrary JAR or applying an unrelated Java update is not a documented substitute.

Temporary risk reduction if patching is delayed

Oracle states that blocking the network protocols required by an attack may reduce risk until patches are applied. For this CVE that means HTTP and HTTPS paths to affected deployments, and blocking them may break application functionality. Oracle recommends testing such changes on nonproduction systems. Blocking also does not correct the underlying vulnerability. Oracle's guidance on removing unnecessary privileges does not apply here because the attack requires no privileges.

Why NVD and some trackers may not show a fix

When this was checked, NVD still returned "CVE ID Not Found" for this CVE, and some aggregators reported no fix available. This appears to be an ingestion delay. Oracle's advisory and its text-form risk matrix both list CVE-2026-91548 as addressed in the November 2026 CSPU.

Affected Systems and Versions

  • Vendor: Oracle Corporation (the "Unknown" vendor field in some feeds refers to Oracle)
  • Product: Oracle Platform Security for Java, Oracle Fusion Middleware
  • Component: Centralized Thirdparty Jars
  • Affected supported versions: 12.2.1.4.0 and 14.1.2.0.0
  • Vulnerable configuration: any affected deployment reachable by an attacker over HTTP or HTTPS, with no authentication or user interaction required

Oracle warns that additional products may be significantly impacted through the scope change but does not enumerate them. Products built on OPSS, such as WebLogic Server, SOA applications, WebCenter, Oracle ADF applications, and Oracle Entitlements Server, are architecturally related, but the CVE record does not list them as independently affected.

Vendor Security History

Oracle has a documented patch and emergency alert process. A relevant recent example is CVE-2025-61882 in Oracle E Business Suite, for which Oracle issued a security alert initially released on October 4, 2025, recommended prompt updates, and published observed indicators of compromise.

Google Threat Intelligence Group and Mandiant documented an Oracle E Business Suite exploitation and extortion campaign that used the CL0P extortion brand and showed similarities to suspected FIN11 tooling. GTIG did not formally attribute the activity to a tracked group and cautioned that the exact vulnerabilities or exploit chains corresponding to CVE-2025-61882 remained unclear. That case shows why patch availability, observed attacks, and attribution should be treated as separate questions. Nothing in the reviewed reporting connects those actors, tools, or exploit chains to CVE-2026-91548.

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