Executive Summary

Between May 27 and June 9, 2026, the financially motivated threat group ShinyHunters (tracked by Mandiant as UNC6240) exploited a zero-day chain in Oracle PeopleSoft Enterprise PeopleTools versions 8.61 and 8.62, later patched as CVE-2026-35273 (CVSS 9.8). The attack chains three distinct flaws: an unauthenticated server-side request forgery (SSRF) in the Integration Gateway (PSIGW), a loopback-trust bypass in the Environment Management Hub (PSEMHUB), and either an arbitrary file-write for web shell deployment or a malicious XMLDecoder payload for stealthier code execution. Oracle issued an out-of-band patch on June 10; a second, broader campaign targeting universities, healthcare, government, and technology sectors was confirmed by Mandiant in September 2026.

The September wave demonstrated that WAF-based mitigations were bypassed trivially via URL-encoding, underscoring a persistent industry pattern: perimeter controls are insufficient when attackers can manipulate request encoding, and organizations relying on signature-based filtering rather than patching remain exposed. ShinyHunters' data-theft-then-extortion model means affected organizations face both data breach notification obligations and ransom demands simultaneously.

Why This Matters Now

CVE-2026-35273 is actively listed on CISA's Known Exploited Vulnerabilities catalog, and ShinyHunters has already launched a second mass-exploitation wave across six industries. With Oracle PeopleSoft widely deployed in higher education, healthcare, and government, and with attackers demonstrating WAF-bypass via URL-encoding, organizations that have not yet patched or disabled PSEMHUB remain at imminent risk of data theft and extortion with limited detection opportunity.

Attack Path Analysis

Related CVEs

MITRE ATT&CK® Techniques

Potential Compliance Exposure

Sector Implications

Sources

Frequently Asked Questions

CVE-2026-35273 bundles three distinct PeopleSoft flaws: an unauthenticated SSRF in the Integration Gateway, a loopback-trust bypass in the Environment Management Hub, and either a path-controlled file-write or a malicious XMLDecoder payload for code execution. The 9.8 score reflects unauthenticated network-reachable remote code execution with no user interaction required.

Cloud Native Security Fabric Mitigations and ControlsCNSF

Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.

Aviatrix Zero Trust CNSF is directly relevant to this incident because the attack chain depended on unrestricted internal reachability between PSIGW, PSEMHUB, backend data stores, and external egress paths. A Zero Trust segmentation fabric would likely have constrained attacker reach at multiple stages, reducing the blast radius from a single exploited gateway to a much smaller, isolated application boundary.

Initial Compromise

Control: Cloud Native Security Fabric (CNSF)

Mitigation: A Zero Trust fabric enforcing workload-aware perimeter policies could likely reduce the reachability of internal interfaces like PSEMHUB from public-facing application endpoints, making the SSRF pivot path harder to complete even when the application-layer vulnerability exists.

Privilege Escalation

Control: Zero Trust Segmentation

Mitigation: Zero Trust segmentation enforcing identity-scoped access between the integration gateway and application management components could likely constrain the trust relationship that allowed PSEMHUB to accept and act on attacker-controlled payloads, reducing the scope of privilege available to a compromised request.

Lateral Movement

Control: East-West Traffic Security

Mitigation: East-west enforcement policies at the workload level could likely reduce the number of backend systems reachable from a compromised PeopleSoft host, constraining lateral pivot paths to only those explicitly permitted between defined workload identities rather than allowing broad application-tier connectivity by default.

Command & Control

Control: Multicloud Visibility & Control

Mitigation: Centralized traffic visibility across the application environment could likely surface anomalous inbound command patterns or unexpected interactive sessions to the PeopleSoft tier, helping operations teams identify persistent web shell activity that might otherwise blend into normal application traffic.

Exfiltration

Control: Egress Security & Policy Enforcement

Mitigation: Egress policy enforcement restricting outbound connections from PeopleSoft workloads to explicitly approved external destinations could likely constrain the attacker's ability to transfer data to unauthorized infrastructure, reducing the volume or completeness of exfiltration even when the compromised host is already under attacker control.

Impact (Mitigations)

Had earlier segmentation and egress controls been in place, the scope of data reachable from a single compromised PeopleSoft instance would likely have been narrower, reducing the volume of sensitive records available for weaponization and potentially limiting attacker leverage to a smaller subset of affected organizations.

Impact at a Glance

Affected Business Functions

  • Student Information Systems and Academic Record Management (Higher Education)
  • Enterprise Resource Planning (ERP) and HR/Payroll Services
  • Healthcare Patient Administration and Billing Systems
  • Government Citizen Services and Administrative Portals
Operational Disruption

Estimated downtime: 14 days

Financial Impact

Estimated loss: N/A

Data Exposure

The exploitation of CVE-2026-35273 by ShinyHunters (UNC6240) across two distinct campaign waves resulted in unauthorized access to PeopleSoft-hosted data spanning multiple sectors. Confirmed and probable exposed data categories include: personally identifiable information (PII) of students and faculty from targeted universities; employee records including HR, payroll, and benefits data from technology, IT services, and government entities; patient administrative and billing records from healthcare organizations; and enterprise authentication credentials reachable from the compromised PeopleSoft service account tier. The threat actor's established pattern of data theft followed by extortion demands indicates that exfiltrated data was likely leveraged for ransom negotiations. Web shells planted during exploitation may have enabled persistent access and secondary credential harvesting across dozens of affected systems worldwide. Financial loss figures are not publicly confirmed but extortion payments and incident response costs for dozens of affected organizations are expected to be substantial.

Recommended Actions

  • • Apply Zero Trust Segmentation (ZTMM.Network, NIST.800-53.AC-6) to enforce identity-based microsegmentation around PeopleSoft application tiers, preventing the compromised PSIGW service from freely reaching PSEMHUB or any backend system without explicit policy authorization — loopback-based trust chains should never substitute for verified network policy.
  • • Deploy Egress Security & Policy Enforcement (ZTMM.Data, NIST.CSF.PR.DS-5) with FQDN filtering and outbound traffic controls on all PeopleSoft application hosts to block data exfiltration to unauthorized external destinations, terminating ShinyHunters' data-theft pipeline before bulk transfer completes.
  • • Enable East-West Traffic Security (ZTMM.Network, NIST.800-53.SC-7) to inspect and restrict workload-to-workload flows from PeopleSoft application servers to databases, internal APIs, and directory services, containing lateral movement radius after initial web shell deployment.
  • • Activate Multicloud Visibility & Control (ZTMM.CrossCutting.Visibility, NIST.800-53.AU-6) with centralized traffic observability to baseline normal PeopleSoft Integration Gateway behavior and alert on anomalous loopback-forwarded requests, repeated malformed path patterns (e.g., URL-encoded /%50SEMHUB/ variants), and unexpected outbound connection spikes indicative of active exploitation or exfiltration.
  • • Deploy Inline IPS with Suricata signatures (NIST.800-53.SI-4, PCI.4.0.6.4.1) covering SSRF exploit patterns, known CVE-2026-35273 request signatures, and web shell traffic indicators on PeopleSoft-facing network segments, providing a defense-in-depth layer that complements but does not replace patching, and use Encrypted Traffic protection (NIST.CSF.PR.DS-2) to ensure exfiltration channels cannot evade inspection through unencrypted transit paths.

Secure the Paths Between Cloud Workloads

A cloud-native security fabric that enforces Zero Trust across workload communication—reducing attack paths, compliance risk, and operational complexity.

Cta pattren Image