Automated Threat Modeling

Brief Summary: CVE-2026-114934, Unauthenticated Data Exposure in Oracle PeopleSoft PeopleTools Integration Broker

A brief summary of CVE-2026-114934, an unauthenticated HTTP vulnerability in the Integration Broker component of Oracle PeopleSoft Enterprise PeopleTools 8.61 through 8.63. The post covers Oracle's disclosed impact, the CVSS scoring discrepancy, and how to confirm the November 2026 CSPU fix using bug 39576556 and My Oracle Support document CPU457.

CVE Analysis

7 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-17

Brief Summary: CVE-2026-114934, Unauthenticated Data Exposure in Oracle PeopleSoft PeopleTools Integration Broker

Introduction

An unauthenticated attacker who can reach PeopleSoft Integration Broker over HTTP may be able to read critical data accessible to PeopleSoft Enterprise PeopleTools and modify some of it, with impact that Oracle says can extend into additional products. Integration Broker brokers messaging and web services between PeopleSoft and external systems, so its HTTP interfaces are built to accept inbound requests. That is why an unauthenticated flaw here in PeopleTools 8.61 through 8.63 deserves prompt attention from PeopleSoft owners.

Oracle fixed the issue, tracked as CVE-2026-114934, in its November 2026 Critical Security Patch Update (CSPU). This post is a short review of what Oracle has disclosed, what can and cannot be concluded from it, and how to confirm the fix is installed.

Technical information

Where Integration Broker sits

Oracle documentation describes Integration Broker as middleware for synchronous and asynchronous messaging between PeopleSoft and third-party systems. It can expose PeopleSoft business logic as web services, and it can also consume or invoke external web services. Architecturally, Oracle places the integration gateway on a PeopleSoft web server and the integration engine on an application server.

In practice, Integration Broker accepts inbound synchronous and asynchronous service operations from external systems and routes them into the application. That describes the product's architecture. It is not a confirmed attack path for this specific CVE.

What Oracle discloses

Oracle's advisory and the PeopleSoft risk matrix describe the vulnerability as follows:

  • Attack vector: network, via HTTP
  • Attack complexity: low. Oracle labels it easily exploitable.
  • Privileges required: none
  • User interaction: none
  • Scope: changed. Attacks may significantly impact additional products.
  • Confidentiality: high, meaning unauthorized access to critical data or complete access to all PeopleTools-accessible data
  • Integrity: low, meaning unauthorized update, insert or delete access to some PeopleTools-accessible data
  • Availability: none

The CVE record and the risk matrix list the following vector with a CVSS 3.1 base score of 9.3:

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

The Notes column for this row in the risk matrix is empty, so Oracle lists no special preconditions or configuration requirements.

Root cause: what is known and what is inferred

PeopleTools is closed source, and Oracle has not published a diff, commit or root-cause write-up. No CWE identifier is assigned in the material we reviewed. The advisory does not describe a vulnerable URL, request format, exploit chain, proof of concept or code.

What we can say is inferred from Oracle's impact language: an unauthenticated HTTP request to Integration Broker leads to broad read access, limited write access, and impact beyond PeopleTools itself. Combined with Integration Broker's role as the inbound messaging gateway, this suggests the fix tightens authentication or authorization on an inbound gateway or listening connector request path. Oracle has not confirmed this, and no published patch diff verifies it, so treat it as a working hypothesis rather than a finding.

Attack flow, as far as the advisory supports it

  1. An attacker identifies a PeopleSoft deployment running PeopleTools 8.61, 8.62 or 8.63 whose Integration Broker is reachable over HTTP.
  2. The attacker sends HTTP requests to Integration Broker without credentials. No action by a legitimate user is needed.
  3. A successful attack yields unauthorized read access to critical data, up to all PeopleTools-accessible data, and unauthorized update, insert or delete access to some of that data.
  4. Because the scope is changed, the impact can extend into additional products beyond PeopleTools.

We are deliberately not filling in the specific endpoint or payload, because none of the source material describes them.

A note on the CVSS score

The scoring sources do not fully agree. The CVE record and the advisory risk matrix list 9.3 with a changed scope (S:C). A separate review of Oracle's CSAF record reported 8.2 with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N, an unchanged scope. The reviewed sources do not explain the difference. Either way, the core properties are the same: network reachable, no authentication, no user interaction, and high confidentiality impact. We recommend checking the scope value directly in Oracle's text-form risk matrix before recording it in internal tracking.

Exploitation status

The sources we examined do not establish active exploitation of this CVE and do not identify a threat actor. The CVE-specific page we reviewed gives no in-the-wild evidence, and the examined CISA Known Exploited Vulnerabilities catalog excerpt does not mention it. No verified public proof of concept was found. This is a limit of the available evidence, not proof that exploitation has not occurred.

Patch information

Oracle has shipped a fix, but obtaining it requires a support contract. The fix is part of the November 2026 Critical Security Patch Update, covers the Integration Broker component of PeopleSoft Enterprise PeopleTools, and applies to all three supported release lines: 8.61, 8.62 and 8.63.

What Oracle has published

Oracle's CSAF record for the November 2026 CSPU contains a vendor_fix remediation entry for this CVE:

  • Oracle Bug ID: 39576556. Use this to match the fix against PeopleTools patch readme and bug fix lists.
  • Affected product: PeopleSoft Enterprise PeopleTools, Oracle product 5085, versions 8.61 through 8.63
  • Remediation category: vendor_fix, available to Oracle customers with valid support contracts
  • Patch availability document: My Oracle Support CPU457. The advisory's Patch Availability table lists the same document for PeopleSoft.

How to read this fix

Oracle CSPUs do not come with a public fixed version string such as a specific 8.6x.yy build. Instead:

  1. The CVE maps to Oracle bug 39576556, the internal tracking number for the Integration Broker fix. Check for this number in the downloaded patch's bug fix list or readme, not just the patch date.
  2. CPU457 is the source of truth for what to install. The My Oracle Support document lists the exact PeopleTools patch for each release line. Because it sits behind a support login, we cannot confirm the specific patch numbers or patch-level builds here.
  3. You need to be on a supported release line. Oracle provides CSPU patches only for versions under Premier or Extended Support. Older releases are not tested against these vulnerabilities, and Oracle warns they are likely affected. A PeopleTools release older than 8.61 has no patch path for this CVE. The only route to a fix is upgrading to a supported line.

Interim measures while the patch is scheduled

Oracle recommends applying CSPU patches as soon as possible. Until they are applied, Oracle states that blocking the network protocols required for an attack may reduce risk, and that removing access for users who do not need it can help where particular privileges or package access are required. Oracle cautions that these changes may break functionality, should be tested on nonproduction systems, and are not long-term fixes.

To confirm coverage, obtain the PeopleTools patch for your release line from CPU457 and verify that its fix list includes bug 39576556.

Affected systems and versions

  • Product: Oracle PeopleSoft Enterprise PeopleTools
  • Component: Integration Broker
  • Affected supported versions: 8.61, 8.62 and 8.63 (8.61 through 8.63)
  • Exposure condition: an attacker with network access to Integration Broker over HTTP, with no authentication or user interaction required
  • Special configuration: none listed. The Notes column in Oracle's risk matrix is empty for this row.
  • Unsupported releases: versions older than 8.61 are not tested by Oracle, are likely affected according to Oracle, and receive no patch

Vendor security history

Oracle publishes Critical Patch Updates, which are usually cumulative and issued quarterly, and smaller Critical Security Patch Updates that deliver high-priority fixes between them for supported on-premises products. Oracle has stated that attackers have sometimes succeeded because customers had not applied patches that were already available. For PeopleSoft specifically, Oracle maintains guidance on locating PeopleSoft security fixes, and PeopleTools updates follow the standard patch process. The record points to an established patch channel, with delayed patching as the main operational risk.

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