On this page (7 sections)

CVE-2026-114862 is a critical vulnerability in the Weblogic component of Oracle PeopleSoft Enterprise PeopleTools. According to the NVD record, an unauthenticated attacker with network access over HTTP can compromise PeopleTools, and the supported versions affected are 8.61 through 8.63.

If your organization runs PeopleSoft for HR, finance or campus systems, or you host it for a client, this is worth checking today. The public record is short, so this article separates what is confirmed from what is not, and focuses on steps you can take now.

What happened

The flaw was published by the National Vulnerability Database on November 17, 2026, and added to the GitHub Advisory Database on November 18, 2026. Both entries list an Oracle security alert, cspunov2026, as a reference. We did not review the contents of that Oracle page, so we cannot say what guidance it contains, and no fixed version is confirmed here.

Only one underlying description exists so far. The NVD text is repeated by the GitHub advisory, so the two should not be counted as independent confirmation. The GitHub entry is also marked unreviewed, and it lists affected and patched versions as unknown.

Technical details

The description calls the issue easily exploitable and says it needs no privileges and no user interaction. In the CVSS vector, that maps to network attack vector, low complexity, no privileges required and no user interaction.

The weakness class is CWE-306, missing authentication for critical functionality. In plain terms, some function that should only be available to a verified user can be reached without logging in. Attackers do not need to guess passwords or trick anyone; they only need to reach the service over HTTP.

The described impact is on confidentiality and integrity, both rated high, and availability is not affected. A successful attack can result in unauthorized creation, deletion or modification of critical data, or all PeopleTools-accessible data, as well as unauthorized access to that data. The record gives no exploit mechanics, and we are not adding any.

Who is affected

  • Organizations running PeopleSoft Enterprise PeopleTools 8.61, 8.62 or 8.63, the supported versions named as affected in the record.
  • Deployments where the PeopleTools web tier, including the Weblogic component, accepts HTTP connections from untrusted networks. The attack vector is network, so internet-facing portals carry the most risk.
  • Hosting providers and agencies that manage PeopleSoft on behalf of clients.
  • Other PeopleTools versions are not mentioned in the research. Do not assume they are safe or affected; check with Oracle.
The research does not report exploitation, but that is not proof that nobody is attacking it. Treat a 9.1 unauthenticated network flaw as urgent.

How to check your exposure

Start by confirming your PeopleTools release. Your PeopleSoft administrator or Oracle documentation will list where the version is shown for your release. Compare the result against 8.61-8.63.

Next, find out who can reach the web tier. From a machine outside your network, run the command below, replacing the hostname with your own. It is read-only and prints only the HTTP status line; getting a status line back means the service is reachable from where you ran it.

Check from an external host whether the PeopleSoft web tier answers over HTTPS (read-only)Shell
curl -sI https://peoplesoft.example.com/ | head -n 1

If you get an HTTP status line back from the internet and you did not intend public access, that is the first thing to restrict. Also review your web server and Weblogic access logs for unusual requests from unfamiliar addresses, particularly requests that succeeded without a login. Look at the period since your last patch cycle.

What to do now

  1. Identify every PeopleSoft system and confirm whether its PeopleTools version is 8.61, 8.62 or 8.63.
  2. Check Oracle's alert at oracle.com/security-alerts/cspunov2026.html, which the NVD and GitHub entries reference, and look for any vendor guidance for your release. Confirm patch details with Oracle rather than third-party summaries.
  3. Once Oracle's guidance for your release is confirmed, apply it in a test environment first, then in production, as soon as your change process allows.
  4. Until then, restrict HTTP access to PeopleSoft to trusted networks or a VPN using firewall rules or your load balancer.
  5. If a web application firewall sits in front of PeopleSoft, review its rules and logging, but do not treat it as a substitute for the vendor fix.
  6. Review access logs and data-change audit records for unexpected creation, deletion or modification of records.
  7. If you find signs of unauthorized access, follow your incident response plan and rotate credentials and secrets used by the application.
Caution. Applying updates and restarting PeopleSoft or Weblogic services causes downtime and can affect integrations. Test first, schedule a maintenance window, and take backups of the database and configuration before changing production.
Tip. Where PeopleSoft does not need to be public, removing internet exposure is the fastest risk reduction. Combine it with the vendor fix rather than choosing one or the other.

Detection and monitoring afterwards

After updating, keep watching. Alert on spikes in requests from a single source to PeopleSoft endpoints, on successful requests that carry no session, and on bulk or off-hours data changes in audit tables. Keep logs long enough to look back, because a flaw like this may be probed before details become widely known.

Also watch the outer layer. Webforta Monitor can alert you to certificate, DNS and header changes on the public hostname, and the free SSL checker lets you confirm the endpoint's certificate is healthy. These do not detect or fix this vulnerability, but they help you notice unexpected changes around an exposed system. For background on filtering traffic in front of an application, see What is a WAF?.

What is still unknown

  • The exact fixed version or patch: the GitHub advisory lists patched versions as unknown, and we did not review Oracle's page.
  • Whether the flaw is exploited in the wild: the research reports no exploitation and no CISA KEV entry.
  • Whether a public proof of concept exists: the GitHub advisory states no known source code.
  • Which exact Weblogic endpoints are involved: the record does not say.

Check Oracle's alert directly for any vendor guidance rather than waiting for secondary coverage.

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.

  1. CVE-2026-114862 - GitHub Advisory Databasegithub.com
  2. CVE-2026-114862: Vulnerability in the PeopleSoft Enterprise PeopleTools product of Oracle PeopleSoft (component: Weblogic).nvd.nist.gov ·
  • Oracle
  • PeopleSoft
  • CVE-2026-114862
  • CWE-306
  • Critical vulnerability