The Zero Day Initiative has published ZDI-26-1039, detailing CVE-2026-35273 — an incorrect authorization vulnerability in Oracle PeopleSoft that allows remote attackers to execute arbitrary code on affected installations. ZDI has assigned this flaw a CVSS score of 9.9, which places it at the absolute top of your patch queue. The advisory indicates the vulnerable register component can be reached without authentication, meaning an attacker with nothing more than network access to the PeopleSoft Internet Architecture (PIA) web tier can potentially execute code in the context of the application server.
Let me be blunt about why this matters: PeopleSoft is not a line-of-business convenience app. It is the system of record for HR, payroll, financials, and student data at thousands of enterprises, universities, and government agencies. It holds SSNs, bank account numbers, salary data, and W-2s. A pre-authentication RCE on the PIA tier is effectively a skeleton key into the most sensitive data your organization owns — and historically, PeopleSoft/WebLogic flaws of this class (the WebLogic deserialization waves being the canonical example) move from disclosure to mass scanning within days, sometimes hours.
If you run PeopleSoft and any portion of the PIA web tier is reachable from the internet — self-service portals, supplier portals, campus portals — treat this as an emergency change. Now.
Technical Analysis
Affected Products and Platforms
- Product: Oracle PeopleSoft (PeopleSoft Enterprise applications running on the PeopleTools platform)
- Affected Component: The
registerfunctionality within the PeopleSoft Internet Architecture (PIA) web tier, which runs on Oracle WebLogic Server - Platforms: All operating systems supported by PeopleTools (Windows, Linux, AIX, Solaris, HP-UX) — the flaw is in the application layer, not the OS
- Advisory: ZDI-26-1039 (http://www.zerodayinitiative.com/advisories/ZDI-26-1039/)
- CVE: CVE-2026-35273
- CVSS: 9.9 (Critical)
How the Vulnerability Works — Defender's View
ZDI classifies this as an incorrect authorization flaw (CWE-863). The specific weakness sits in the register component: a request-handling path that fails to properly enforce authorization checks before performing privileged operations. The practical result is that an unauthenticated remote attacker can invoke functionality that should be gated behind an authenticated session, and leverage that functionality to execute arbitrary code on the underlying application server.
From an attack-chain perspective, expect the following shape:
- Reconnaissance: Attacker fingerprints PeopleSoft by probing for characteristic PIA paths (
/psp/,/psc/, portal endpoints) and PeopleSoft-specific response headers or login pages. - Exploitation: A crafted HTTP request is sent to the
register-related endpoint on the PIA web tier (typically WebLogic listening on 8000/8443 or proxied through 80/443). No credentials or session token are required. - Code Execution: Payload executes in the security context of the WebLogic/PIA service account — frequently
SYSTEMon Windows or a dedicatedpsoft/WebLogic service user on Linux, and in far too many real-world deployments, an account with far broader privileges than it should have. - Post-Exploitation: Historically with ERP-tier RCEs, we see web shell deployment (JSP files dropped into PIA web directories), followed by credential harvesting from configuration files (
psappsrv.cfg, WebLogic config stores), database connector strings, and then lateral movement toward the database tier where the actual crown jewels live.
Exploitation Status
ZDI advisories are published after the vendor has been given the opportunity to patch, and ZDI's 9.9 rating reflects the low exploitation complexity and high impact. At the time of writing there is no public confirmation of in-the-wild exploitation or CISA KEV listing for CVE-2026-35273 — but do not take comfort in that. ZDI advisories routinely include enough technical detail for skilled researchers (and threat actors) to reverse-engineer a working exploit from the patch differential. PeopleSoft's install base is large, slow to patch, and frequently internet-exposed. Assume scanning begins immediately and treat "not yet exploited" as a temporary condition.
Detection & Response
Detection for application-layer RCE against PIA rests on two pillars: web-tier telemetry (access logs, WAF, proxy logs) and host behavior (the application server doing things application servers should never do). The single highest-fidelity signal is the WebLogic/PIA Java process spawning a shell or scripting interpreter. That is almost never legitimate in production.
Sigma Rules
---
title: PeopleSoft WebLogic Java Process Spawning Shell or Script Interpreter
id: 8c1f4e92-7b3a-4d5e-9f21-6a8c0d2e4b71
status: experimental
description: Detects the WebLogic/PIA Java process spawning command shells or scripting interpreters, a high-fidelity indicator of post-exploitation following RCE against Oracle PeopleSoft (e.g. CVE-2026-35273 / ZDI-26-1039).
references:
- http://www.zerodayinitiative.com/advisories/ZDI-26-1039/
- https://attack.mitre.org/techniques/T1059/
author: Security Arsenal
date: 2026/01/15
tags:
- attack.execution
- attack.t1059
- attack.initial_access
- attack.t1190
logsource:
category: process_creation
product: windows
detection:
selection_parent:
ParentImage|endswith:
- '\java.exe'
- '\javaw.exe'
selection_weblogic:
ParentCommandLine|contains:
- 'weblogic'
- 'peoplesoft'
- 'PIA'
selection_child:
Image|endswith:
- '\cmd.exe'
- '\powershell.exe'
- '\pwsh.exe'
- '\wscript.exe'
- '\cscript.exe'
- '\rundll32.exe'
- '\regsvr32.exe'
- '\certutil.exe'
- '\bitsadmin.exe'
- '\curl.exe'
- '\wget.exe'
condition: selection_parent and selection_weblogic and selection_child
falsepositives:
- Rare administrative tooling invoked from PeopleSoft process scheduler custom jobs
level: critical
---
title: Web Shell Dropped in PeopleSoft PIA Web Directory
id: 2d7a9c41-3e58-4b9f-a6d3-1f8e5c0b7a29
status: experimental
description: Detects creation of JSP files in PeopleSoft PIA WebLogic web application directories, consistent with web shell deployment following exploitation of an unauthenticated RCE such as CVE-2026-35273.
references:
- http://www.zerodayinitiative.com/advisories/ZDI-26-1039/
- https://attack.mitre.org/techniques/T1505/003/
author: Security Arsenal
date: 2026/01/15
tags:
- attack.persistence
- attack.t1505.003
logsource:
category: file_event
product: windows
detection:
selection:
TargetFilename|contains:
- '\applications\peoplesoft\PORTAL.war\'
- '\webserv\'
- '\piaroot\'
TargetFilename|endswith:
- '.jsp'
- '.jspx'
- '.war'
filter_legit_deploy:
Image|endswith:
- '\java.exe'
CommandLine|contains:
- 'psadmin'
- 'deploy'
condition: selection and not filter_legit_deploy
falsepositives:
- Legitimate PeopleTools maintenance, custom page deployments, or patch application outside a change window should still be investigated
level: high
---
title: Suspicious Unauthenticated Requests to PeopleSoft Register Endpoint
id: 5b3e8d07-9a14-4c62-bf88-2e7d1a9c4f36
status: experimental
description: Detects HTTP requests to PeopleSoft register-related PIA endpoints originating from external sources, including abnormal HTTP methods and encoded payloads, associated with exploitation attempts against CVE-2026-35273 / ZDI-26-1039.
references:
- http://www.zerodayinitiative.com/advisories/ZDI-26-1039/
- https://attack.mitre.org/techniques/T1190/
author: Security Arsenal
date: 2026/01/15
tags:
- attack.initial_access
- attack.t1190
logsource:
category: webserver
detection:
selection_uri:
cs-uri|contains:
- '/register'
selection_suspicious:
cs-method:
- 'POST'
- 'PUT'
- 'DELETE'
filter_internal:
c-ip|startswith:
- '10.'
- '192.168.'
- '172.16.'
- '172.17.'
- '172.18.'
- '172.19.'
- '172.2'
- '172.30.'
- '172.31.'
condition: selection_uri and selection_suspicious and not filter_internal
falsepositives:
- Legitimate self-registration portals exposed to the internet; tune against known external portal use and expected user agents
level: high
KQL — Microsoft Sentinel / Defender
This hunt assumes PeopleSoft front-end (load balancer / reverse proxy / WAF) logs are ingested into Sentinel via CommonSecurityLog, and EDR telemetry covers the PIA hosts via DeviceProcessEvents and DeviceFileEvents.
// Hunt 1: External requests hitting PeopleSoft register endpoints (potential CVE-2026-35273 probing)
let timeframe = 14d;
CommonSecurityLog
| where TimeGenerated > ago(timeframe)
| where RequestURL contains "register" or RequestURL contains "psp/" or RequestURL contains "psc/"
| where notipv4ranges("internal")
| where SourceIP !startswith "10." and SourceIP !startswith "192.168." and SourceIP !startswith "172."
| summarize RequestCount = count(),
DistinctMethods = make_set(RequestMethod),
ResponseCodes = make_set(ApplicationProtocol),
FirstSeen = min(TimeGenerated),
LastSeen = max(TimeGenerated)
by SourceIP, RequestURL, DestinationHostName
| order by RequestCount desc;
// Hunt 2: WebLogic/PIA Java process spawning shells or script interpreters (post-exploitation behavior)
let timeframe = 14d;
DeviceProcessEvents
| where TimeGenerated > ago(timeframe)
| where InitiatingProcessFileName =~ "java.exe" or InitiatingProcessFileName =~ "javaw.exe"
| where InitiatingProcessCommandLine has_any ("weblogic", "peoplesoft", "PIA", "webserv")
| where FileName in~ ("cmd.exe", "powershell.exe", "pwsh.exe", "wscript.exe", "cscript.exe",
"rundll32.exe", "certutil.exe", "bitsadmin.exe", "curl.exe", "wget.exe",
"whoami.exe", "net.exe", "ipconfig.exe")
| project TimeGenerated, DeviceName, InitiatingProcessAccountName,
InitiatingProcessCommandLine, FileName, ProcessCommandLine, SHA256
| order by TimeGenerated desc;
// Hunt 3: New JSP files appearing in PeopleSoft web directories (web shell staging)
let timeframe = 14d;
DeviceFileEvents
| where TimeGenerated > ago(timeframe)
| where FolderPath has_any ("PORTAL.war", "webserv", "peoplesoft", "applications")
| where FileName endswith ".jsp" or FileName endswith ".jspx"
| where ActionType == "FileCreated"
| project TimeGenerated, DeviceName, FolderPath, FileName, InitiatingProcessFileName,
InitiatingProcessAccountName, SHA256
| order by TimeGenerated desc;
Velociraptor VQL
Use this hunt artifact across your PIA fleet to surface both post-exploitation process behavior and web shell artifacts in one sweep.
-- CVE-2026-35273 Hunt: PeopleSoft PIA post-exploitation indicators
-- Identifies WebLogic Java processes spawning shells AND JSP files
-- created in PIA web directories within the last 14 days.
LET suspicious_children = SELECT Pid, Ppid, Name, Exe, CommandLine, Username, CreateTime
FROM pslist()
WHERE CommandLine =~ '(?i)(cmd\.exe|powershell|pwsh|wscript|cscript|rundll32|certutil|bitsadmin|curl|wget|whoami|net user|/bin/(ba)?sh)'
LET psoft_parents = SELECT Pid, Name, CommandLine, Username, CreateTime
FROM pslist()
WHERE CommandLine =~ '(?i)(weblogic|peoplesoft|webserv|PIA)'
LET proc_hits = SELECT c.Pid AS ChildPid, c.Name AS ChildName, c.CommandLine AS ChildCmdLine,
c.Username AS ChildUser, c.CreateTime AS ChildStart,
p.Name AS ParentName, p.CommandLine AS ParentCmdLine
FROM suspicious_children c
JOIN psoft_parents p ON c.Ppid = p.Pid
LET webshell_hits = SELECT FullPath, Size, Mtime, Ctime
FROM glob(globs=['C:/psoft/**/applications/**/PORTAL.war/**/*.jsp',
'C:/psoft/**/webserv/**/*.jsp',
'/opt/psoft/**/applications/**/PORTAL.war/**/*.jsp',
'/opt/psoft/**/webserv/**/*.jsp',
'/home/psoft/**/webserv/**/*.jsp'])
WHERE Mtime > now() - 1209600
SELECT * FROM if(condition=proc_hits, then={SELECT * FROM proc_hits}, else={SELECT * FROM webshell_hits})
Remediation Script
The following Bash script performs a defensive posture check on Linux-based PeopleSoft PIA hosts: it inventories PIA web directories for recently modified JSP files, checks for suspicious child processes of the WebLogic JVM, reviews access logs for register endpoint hits from external sources, and verifies whether the latest Oracle Critical Patch Update (CPU) has been applied by comparing PeopleTools patch levels. Run it read-only first; the commented hardening section restricts egress from the app tier.
#!/bin/bash
# CVE-2026-35273 / ZDI-26-1039 - PeopleSoft PIA triage and posture check
# Run as root or the PeopleSoft service account on PIA (WebLogic) hosts.
PS_HOME=${PS_HOME:-/opt/psoft/pt854}
WEBSERV_DIR=${WEBSERV_DIR:-/opt/psoft/webserv}
DAYS=14
echo "=== [1] PeopleTools version / patch level ==="
if [ -f "$PS_HOME/versions.txt" ]; then cat "$PS_HOME/versions.txt"; else
find "$PS_HOME" -maxdepth 2 -name "version*" -o -name "*.versions" 2>/dev/null | head -20; fi
echo "=== [2] Recently modified JSP/WAR files in PIA web directories (last ${DAYS} days) ==="
find "$WEBSERV_DIR" "$PS_HOME" -type f \( -name "*.jsp" -o -name "*.jspx" -o -name "*.war" \) -mtime -${DAYS} -ls 2>/dev/null
echo "=== [3] WebLogic/PIA Java processes with suspicious children ==="
for pid in $(pgrep -f 'weblogic|peoplesoft|PIA'); do
children=$(ps --ppid "$pid" -o pid,comm,args 2>/dev/null | grep -Ei 'sh$|bash|dash|python|perl|curl|wget|nc$|ncat')
[ -n "$children" ] && echo "[!] Parent PID $pid spawned:" && echo "$children"
done
echo "=== [4] External requests to register endpoints in access logs ==="
grep -hEi 'register' "$WEBSERV_DIR"/*/servers/*/logs/access.log 2>/dev/null | \
grep -Ev '^(10\.|192\.168\.|172\.(1[6-9]|2[0-9]|3[01])\.)' | tail -50
echo "=== [5] Outbound connections from WebLogic JVM (egress check) ==="
for pid in $(pgrep -f 'weblogic|peoplesoft'); do
ss -tup 2>/dev/null | grep "pid=$pid" | grep -v 'ESTAB.*:80\|:443' | head -10
done
# --- Optional hardening (uncomment deliberately, test in lower env first) ---
# Block egress from the PIA tier except to the database tier and update sources:
# iptables -A OUTPUT -m owner --uid-owner <psoft_uid> -p tcp -d <db_subnet>/24 --dport 1521 -j ACCEPT
# iptables -A OUTPUT -m owner --uid-owner <psoft_uid> -j DROP
# Restrict register endpoint at the reverse proxy until patched:
# nginx: location ~* /register { deny all; }
# Apache: <LocationMatch "/register"> Require all denied </LocationMatch>
echo "=== Triage complete. Cross-reference JSP findings against change records. ==="
Remediation
-
Patch immediately via the Oracle Critical Patch Update. Oracle delivers PeopleSoft fixes through its quarterly CPU program and PeopleTools patch releases. Identify the CPU containing the fix for CVE-2026-35273 (reference the ZDI advisory and Oracle's Security Alert page at https://www.oracle.com/security-alerts/), pull the corresponding PeopleTools patch from My Oracle Support, and apply it to all PIA tiers — development, test, and production, in that order, on an emergency change cadence. Do not wait for the next scheduled maintenance window for internet-facing instances.
-
If patching must be deferred, block the attack path at the edge. The most effective interim mitigation is to deny external access to
register-related URI paths at your reverse proxy, load balancer, or WAF. If your organization legitimately exposes self-registration functionality, gate it behind IP allowlisting, VPN, or an identity-aware proxy until the patch lands. -
Remove PeopleSoft from direct internet exposure where possible. Self-service and supplier portals are the common justification for internet-facing PIA. If the business requirement stands, the PIA tier must sit behind a hardened reverse proxy/WAF with request inspection — WebLogic should never answer raw internet traffic directly.
-
Hunt before you patch. Exploitation may have preceded your patch. Run the KQL hunts and the VQL sweep above across the last 30 days of telemetry. Specifically validate: no unexpected JSP files in
PORTAL.warandwebservdirectories, no shells parented to the WebLogic JVM, and no anomalous outbound connections from the app tier. Any positive finding converts this from a patching exercise into an IR engagement — preserve memory and disk images before touching the host. -
Reduce post-exploitation blast radius. Run WebLogic/PIA under a least-privilege service account (never SYSTEM, never a domain admin), segment the app tier so it can only reach the database tier on required ports, and block outbound internet access from PIA hosts. An RCE that cannot call home and cannot move laterally is dramatically less valuable to an attacker.
-
Rotate credentials if compromise is suspected. PeopleSoft configuration files and WebLogic stores contain database connection strings and service credentials. If any indicator of exploitation is found, rotate database service accounts, integration credentials, and any credentials cached on the PIA host — assume they were read.
-
Verify and monitor continuously. After patching, confirm the PeopleTools patch level with your DBA/PeopleSoft admin team, re-run the posture script, and keep the Sigma rules and KQL hunts above in production for at least 90 days to catch exploitation of any unpatched stragglers or shadow instances.
Related Resources
Security Arsenal Penetration Testing Services AlertMonitor Platform Book a SOC Assessment vulnerability-management Intel Hub
Is your security operations ready?
Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.