# CVE-2026-61205: Missing authorization in PeopleSoft Enterprise SCM Purchasing

> Unauthenticated attackers can modify or read critical data in PeopleSoft Enterprise SCM Purchasing via HTTP.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 5 Aug 2026
- **Also known as:** GHSA-v5r8-j7hf-mg66

## What is CVE-2026-61205?

CVE-2026-61205 is a high-severity missing authorization vulnerability in Oracle Corporation PeopleSoft Enterprise SCM Purchasing, published on 21 Jul 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 SCM Purchasing product of Oracle PeopleSoft (component: Purchasing).   The supported version that is affected is 9.2. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise PeopleSoft Enterprise SCM Purchasing.  Successful attacks of this vulnerability can result in  unauthorized creation, deletion or modification access to critical data or all PeopleSoft Enterprise SCM Purchasing accessible data as well as  unauthorized read access to a subset of PeopleSoft Enterprise SCM Purchasing accessible data. CVSS 3.1 Base Score 8.2 (Confidentiality and Integrity impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N).

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Oracle Peoplesoft Enterprise Scm Purchasing.

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

No fix has been published for CVE-2026-61205 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-61205 being exploited?

There is no known exploitation of CVE-2026-61205 in the wild and no public exploit code.

## Other vulnerabilities in Oracle Corporation PeopleSoft Enterprise SCM Purchasing

- [CVE-2026-34295](https://insights.sbomify.com/CVE-2026-34295/): Missing authorization in PeopleSoft Enterprise SCM Purchasing (medium 6.5)
- [CVE-2020-2906](https://insights.sbomify.com/CVE-2020-2906/): Information disclosure in PeopleSoft Enterprise SCM Purchasing (medium 6.5)
- [CVE-2018-2671](https://insights.sbomify.com/CVE-2018-2671/): Information disclosure in PeopleSoft Enterprise SCM Purchasing (medium 6.5)
- [CVE-2017-3521](https://insights.sbomify.com/CVE-2017-3521/): Missing authorization in PeopleSoft Enterprise SCM Purchasing (medium 6.5)
- [CVE-2025-21561](https://insights.sbomify.com/CVE-2025-21561/): Missing authorization in PeopleSoft Enterprise SCM Purchasing (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-61205 is a high-severity missing authorization vulnerability in Oracle Corporation PeopleSoft Enterprise SCM Purchasing, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-61205 in the wild and no public exploit code.

Affected product: Oracle Corporation PeopleSoft Enterprise SCM Purchasing. 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-61205/ (Markdown: https://insights.sbomify.com/CVE-2026-61205/index.md)
```

## Sources

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

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