On this page (7 sections)
A critical vulnerability, CVE-2026-114934, has been published for the Integration Broker component of Oracle PeopleSoft Enterprise PeopleTools. According to the NVD entry, an unauthenticated attacker with network access over HTTP can compromise the product, and the flaw is described as easily exploitable.
If you run a PeopleSoft system on PeopleTools 8.61, 8.62 or 8.63, especially one reachable from the internet or from partner networks, this deserves prompt attention. The public record is thin so far, so this article separates what is confirmed from what is not.
What is known about CVE-2026-114934
The NVD record, published on 2026-11-17, describes a vulnerability in the Integration Broker component of PeopleSoft Enterprise PeopleTools. Supported affected versions are 8.61 through 8.63. The attacker needs no credentials and no user interaction, only network access over HTTP.
The record also notes a scope change: although the flaw sits in PeopleTools, attacks may significantly impact additional products. In practice that means you should think about the systems that depend on your PeopleTools installation, not only PeopleTools itself.
Technical details and impact
The vector breaks down as follows, based on the CVSS values published in the record:
| Metric | Value | Plain meaning |
|---|---|---|
| Attack vector (AV) | Network | Reachable remotely over HTTP |
| Attack complexity (AC) | Low | No special conditions needed |
| Privileges required (PR) | None | No login needed |
| User interaction (UI) | None | No victim action needed |
| Scope (S) | Changed | Impact can extend beyond PeopleTools |
| Confidentiality (C) | High | Complete access to PeopleTools-accessible data |
| Integrity (I) | Low | Some unauthorized update, insert or delete |
| Availability (A) | None | No availability impact stated |
Per the NVD description, successful attacks can result in unauthorized access to critical data, or complete access to all PeopleTools-accessible data, plus unauthorized update, insert or delete access to some of that data. The research does not give the underlying weakness class (no CWE is listed), the exact request path, or any proof of concept, so those details are unknown.
Who is exposed
- Organizations running PeopleSoft Enterprise PeopleTools 8.61, 8.62 or 8.63.
- Systems where PeopleSoft can be reached over HTTP from the internet, a partner network or a flat internal network, since the flaw is exploitable by an unauthenticated attacker with network access via HTTP.
- Environments where PeopleTools can reach sensitive data, since the stated impact includes complete access to all PeopleTools-accessible data.
Exploitation status
No source in the research reports active exploitation, a public exploit, or a listing in CISA's Known Exploited Vulnerabilities catalog (the KEV field for this CVE is empty). That means exploitation is unconfirmed, not ruled out. Only one independent publisher covers this story so far, and the only primary source provided is the NVD record. Treat a CVSS 9.3 unauthenticated network flaw as something to fix quickly regardless.
How to check your exposure
Start by confirming your PeopleTools release on every instance, including test and development, using your normal PeopleSoft administration process or Oracle's documentation. You are looking for releases 8.61, 8.62 or 8.63. The research does not provide a specific command or query for this, so use the method your team already trusts.
Next, find out where PeopleSoft is reachable. From a host outside your trusted network, check whether your PeopleSoft web server answers on its HTTP or HTTPS ports, and review your firewall and load balancer rules for paths that lead to it. Your own web server logs can show whether unfamiliar sources have been sending unusual requests.
What to do now
- Identify every PeopleSoft instance (production, test, development) and record its PeopleTools version.
- Open the Oracle security alert referenced by NVD at https://www.oracle.com/security-alerts/cspunov2026.html and confirm there which patch or fixed version applies to your release, since its contents are not included in the research.
- Apply the fix Oracle specifies to 8.61, 8.62 and 8.63 systems, starting with internet-facing and partner-facing ones, after testing in a non-production copy.
- Until patched, restrict network access to PeopleSoft web endpoints to known partner IP ranges or a VPN.
- Review web server and application logs since 2026-11-17 for unusual unauthenticated requests, and keep the logs.
- If you see signs of unauthorized access, treat the system as compromised: rotate credentials and integration secrets, and follow your incident process.
- Re-check the NVD record and Oracle's advisory for updates on exploitation or additional fixed versions.
Detection and monitoring afterwards
Because the public details are limited, rely on behavior rather than signatures. Watch for spikes of unauthenticated HTTP requests to PeopleSoft, requests from addresses that have never contacted your system, and unexpected data changes. Forward web tier and database audit logs to a central place so you can look back if more details emerge.
You can also use outside-in checks to confirm what your PeopleSoft hostname exposes to the internet. A Webforta scan of a site you verify gives a read-only view of externally visible services, and monitoring can alert you to certificate, DNS or header changes on the hostname. These help with visibility; they do not tell you whether this specific flaw is present, so the vendor patch remains the fix. For general habits on limiting exposure, see our guide to small business website security.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
