CVSS base score: 9.8 (Critical) vendor CNA · v3.1
Score assigned by the vendor's own CVE Numbering Authority (CNA); CISA's Vulnrichment program adds a score only when the CNA omits one. Vulnrichment source record →
Oracle PeopleSoft Enterprise PeopleTools Missing Authentication for Critical Function Vulnerability
Vendor: Oracle Product: PeopleSoft Enterprise PeopleTools
Oracle PeopleSoft Enterprise PeopleTools contains a missing authentication for critical function vulnerability which could allow an unauthenticated attacker to obtain takeover of PeopleSoft Enterprise PeopleTools.
| Date | Source | Article |
|---|---|---|
| 2026-10-28 | The Hacker News | ShinyHunters-Exploited Oracle PeopleSoft Zero-Day Turns Out to Be Three Chained Flaws |
| 2026-09-26 | BleepingComputer | ShinyHunters uses WAF bypass trick in Oracle PeopleSoft attacks |
| 2026-09-26 | The Hacker News | Attackers Bypass WAFs to Exploit Oracle PeopleSoft Flaw and Deploy Web Shells |
| 2026-08-26 | Kaspersky Securelist | Exploits and vulnerabilities in Q2 2026 |
| 2026-06-25 | FortiGuard Labs Threat Signal | Oracle PeopleSoft Zero-Day |
| 2026-06-24 | Trend Micro ZDI | ZDI-26-387: Oracle PeopleSoft HttpListeningConnector Server-Side Request Forgery Vulnerability |
| 2026-06-24 | Trend Micro ZDI | ZDI-26-388: Oracle PeopleSoft HubMBeanPersistance Deserialization of Untrusted Data Remote Code Execution Vulnerability |
| 2026-06-24 | Trend Micro ZDI | ZDI-26-389: Oracle PeopleSoft ExecuteProcessActivityCommand External Control of File Path Remote Code Execution Vulnerability |
| 2026-06-15 | Check Point Research | 15th June – Threat Intelligence Report |
Articles from monitored vendor research blogs and security news feeds that specifically mention this CVE. Coverage begins when feed monitoring started; earlier articles are not indexed.
| Date | Advisory | Issuer |
|---|---|---|
| 2026-06-12 | CISA Adds One Known Exploited Vulnerability to Catalog | CISA |
Each milestone comes from a different source, so gaps between them are gaps in what those sources publish, not evidence that nothing happened. EPSS history for this CVE holds 70 points from 2026-06-13, tracked daily from 2026-09-09; earlier points are weekly, which dates a spike to within a week. Peak probability 96.7% on 2026-10-12.
Check whether a specific version is affected →
What each source publishes about which product versions carry this vulnerability, kept as written rather than merged. Absence here means no source has published applicability data, not that nothing is affected.
Coverage across public collections only: Nuclei and OpenVAS NVT (scan);
Snort and Suricata ET Open (network); Sigma and YARA (host/SIEM);
Metasploit, Exploit-DB, public GitHub repositories and NVD exploit references (exploit). Absence
here means nothing public was found, not that detection is impossible.
GitHub PoC repositories are collected automatically by
PoC-in-GitHub (CC0) and filtered to repositories that are
still online, contain code, and are starred or at least two weeks old. They are
still not vetted: some are fakes and some are malware. Treat
them as evidence that code was published, not as code to run.
NVD exploit references are links NVD's analysts tag as exploits; they confirm
an exploit was referenced but carry no date. This product uses data from the
NVD but is not endorsed or certified by the NVD.
OpenVAS coverage derives from the Greenbone Community Feed, made available
under the Open Database License (ODbL) v1.0;
its individual Vulnerability Tests are licensed
GNU GPL v2.
| First seen | Tool | Evidence | Earliest reference |
|---|---|---|---|
| 2026-06-12 | GitHub PoC | Unvetted — public repository | 0xBlackash/CVE-2026-35273 +2 more |
| 2026-06-16 | Nuclei | Direct — curated exploit code | CVE-2026-35273.yaml |
Metasploit is dated by the first commit of the module file, Exploit-DB by its publication date, and GitHub repositories by their creation date. GitHub PoC repositories are filtered (still online, contain code, starred or at least two weeks old) but not vetted: some are fakes and some are malware, so they show that code was published, not that it works or is safe to run. Evidence tiers are explained on the About page.
| If the asset is | Remediate within | Table 1 row |
|---|---|---|
| Publicly exposed | 3 days + forensic triage → 2026-06-15 | 1 of 16 |
| Not publicly exposed | 3 days + forensic triage → 2026-06-15 | 9 of 16 |
BOD 26-04 replaced the single KEV deadline of BOD 22-01 with four inputs: whether the asset is publicly exposed, KEV status, whether exploitation is automatable, and technical impact. Exposure belongs to each agency's asset, not to the CVE, so both outcomes are shown. Automatable and technical impact come from the CISA assessment above. Days are calendar days; for KEV entries the clock starts on the date it was added. Agencies make the final exposure call asset by asset, and may set shorter timelines.
Defensive techniques inferred by MITRE D3FEND from the underlying weakness (CWE-306) — general hardening and detection guidance for this weakness class, not a vendor patch for this specific CVE.
CVE.org record → NVD entry → CISA KEV catalog → FortiGuard Labs → Rapid7 AttackerKB →