The Encoded PSEMHUB Path That Broke CVE-2026-35273 WAF Defenses
The renewed ShinyHunters campaign against CVE-2026-35273 showed how a control can look correct in a policy and fail in production. Mandiant observed requests with /%50SEMHUB/ instead of /PSEMHUB/. The encoded character reached the vulnerable PeopleSoft servlet while string-based WAF rules missed the path.
This detail matters beyond one attack signature. Web application firewalls often inspect the request target before the application performs its own decoding. A mismatch between those two views creates a bypass opportunity.
Vulnerability overview
CVE-2026-35273 affects Oracle PeopleSoft Enterprise PeopleTools 8.61 and 8.62. Oracle issued an out-of-band fix on 2026-06-10 for a vulnerability that can be exploited remotely without authentication and can lead to remote code execution.
NVD records CVSS 3.1 9.8. The Zero Day Initiative documented a chain involving server-side request forgery and the Environment Management Hub. Mandiant later reported a renewed ShinyHunters campaign that modified the request path to evade path-based WAF controls.
Mechanism and exploitation conditions
The Integration Gateway forwards a request to an attacker-controlled destination. When the destination is 127.0.0.1, the Environment Management Hub treats the connection as local because loopback appears in its allowed-host list.
From the hub, the attacker uses administrative file operations to write a web shell or XML processed by Java XMLDecoder. The encoded PSEMHUB path is not the root vulnerability. It is a delivery technique that prevents a proxy rule from recognizing the sensitive route.
Defenders need to account for percent-encoding, duplicate encoding, path normalization and routing differences among the WAF, reverse proxy and PeopleSoft application server.
Impact
An attacker who reaches the hub can execute code in the PeopleSoft service account. That account may reach application files, database connection data and integrated systems.
The campaign used the access for data theft and extortion. A system protected only by a literal path block can remain exploitable even when the proxy reports that the vulnerable endpoint is blocked.
Affected products and scope
Review every PeopleSoft Enterprise PeopleTools 8.61 and 8.62 deployment that has an Integration Gateway and Environment Management Hub. Include internal application servers because the attack can use an already compromised network position to launch the first request.
Audit WAF configurations for rules that compare an undecoded path with /PSEMHUB/. Check whether the product normalizes requests before or after policy evaluation. Record which component receives the final request and whether the path is logged in a form that supports incident review.
Exposure context
ZoomEye returned 3,298 matches for app="Oracle PeopleSoft" and 0 for the exact CVE query during this review. Product matches show observable PeopleSoft interfaces. They do not prove that PSEMHUB is exposed or that a particular WAF rule is present.
The external result is a starting point for network and application ownership review. The internal request path, component deployment and patch level define the actual exploitation risk.
Remediation and mitigations
Apply Oracle's Security Alert fix. Treat WAF changes as a temporary reduction in reachability. Configure path checks after canonical decoding and reject ambiguous encodings when they are not required by a legitimate integration.
Restrict administrative routes to trusted networks and separate the gateway's outbound request policy from ordinary user traffic. Monitor internal loopback requests to PSEMHUB and unusual gateway destinations. Review WAF logs for the encoded path and related variants.
If an encoded request reached the application during the campaign period, investigate the host for a web shell, unexpected XML and service-account execution. Preserve evidence before cleanup and rotate credentials reachable from the PeopleSoft tier. Patching and WAF hardening close different gaps and should both be verified.
Top comments (0)