# CVE-2026-35273: Oracle PeopleSoft Enterprise PeopleTools Missing Authentication for Critical Function

> Unauthenticated attackers can bypass authentication to fully compromise PeopleSoft Enterprise PeopleTools via HTTP.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 12 Jun 2026 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jun 2026
- **Updated:** 4 Aug 2026
- **Also known as:** GHSA-25mw-359m-f6rj

## What is CVE-2026-35273?

CVE-2026-35273 is a critical authentication bypass vulnerability in Oracle Peoplesoft Enterprise Peopletools, published on 11 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the PeopleSoft Enterprise PeopleTools product of Oracle PeopleSoft (component: Updates Environment Management). Supported versions that are affected are 8.61 and 8.62. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise PeopleSoft Enterprise PeopleTools. Successful attacks of this vulnerability can result in takeover of PeopleSoft Enterprise PeopleTools. CVSS 3.1 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-35273?

It affects 1 product.


Products: Oracle Peoplesoft Enterprise Peopletools.

## How do I fix CVE-2026-35273?

No fix has been published for CVE-2026-35273 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 15 Jun 2026.

## Is CVE-2026-35273 being exploited?

Yes. Attackers have exploited CVE-2026-35273 in the wild since at least 12 Jun 2026, including in ransomware campaigns.

Public exploit code:

- CVE-2026-35273 (github_poc): https://github.com/HORKimhab/CVE-2026-35273
- CVE-2026-35273 (github_poc): https://github.com/0xredash/CVE-2026-35273
- CVE-2026-35273 - Oracle PeopleSoft PeopleTools Unauthenticated RCE Scanner (github_poc): https://github.com/12hrformat/CVE-2026-35273-POC
- https://github.com/rayo0009/CVE-2026-35273-Oracle-PeopleSoft-PeopleTools-Zero-Day- (github_poc): https://github.com/rayo0009/CVE-2026-35273-Oracle-PeopleSoft-PeopleTools-Zero-Day-
- Oracle PeopleSoft PeopleTools PSEMHUB - Pre-Auth Java Deserialization RCE (nuclei): http/cves/2026/CVE-2026-35273.yaml

## Other vulnerabilities in Oracle Peoplesoft Enterprise Peopletools

- [CVE-2026-60821](https://insights.sbomify.com/CVE-2026-60821/): Auth bypass in PeopleSoft Enterprise PeopleTools (critical 9.8)
- [CVE-2022-21543](https://insights.sbomify.com/CVE-2022-21543/): Auth bypass in PeopleSoft Enterprise PT PeopleTools (critical 9.8)
- [CVE-2017-10366](https://insights.sbomify.com/CVE-2017-10366/): Auth bypass in PeopleSoft Enterprise PT PeopleTools (critical 9.8)
- [CVE-2026-101420](https://insights.sbomify.com/CVE-2026-101420/): Vulnerability in the PeopleSoft Enterprise PeopleTools product of Oracle PeopleSoft (component: SQR). (critical 9.6)
- [CVE-2026-83017](https://insights.sbomify.com/CVE-2026-83017/): Auth bypass in PeopleSoft Enterprise PeopleTools (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-35273 and fix it if it is affected.

What it is: CVE-2026-35273 is a critical authentication bypass vulnerability in Oracle Peoplesoft Enterprise Peopletools, published on 11 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2026-35273 in the wild since at least 12 Jun 2026, including in ransomware campaigns.

Affected product: Oracle Peoplesoft Enterprise Peopletools. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-35273/ (Markdown: https://insights.sbomify.com/CVE-2026-35273/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-35273
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-35273
- OSV: https://osv.dev/vulnerability/CVE-2026-35273

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-35273/
Summaries are generated and may contain mistakes; the official description above is the record.