# CVE-2026-61307: Auth bypass in PeopleSoft Enterprise CC Common Application Objects

> Unauthenticated attackers can compromise PeopleSoft Enterprise CC Common Application Objects via network access, leading to full system takeover.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Aug 2026
- **Updated:** 21 Aug 2026
- **Also known as:** GHSA-vxwc-f926-28q5

## What is CVE-2026-61307?

CVE-2026-61307 is a high-severity authentication bypass vulnerability in Oracle Corporation PeopleSoft Enterprise CC Common Application Objects, published on 18 Aug 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 CC Common Application Objects product of Oracle PeopleSoft (component: Common Application Objects).   The supported version that is affected is 9.2. Difficult to exploit vulnerability allows unauthenticated attacker with network access via Oracle Net to compromise PeopleSoft Enterprise CC Common Application Objects.  Successful attacks of this vulnerability can result in takeover of PeopleSoft Enterprise CC Common Application Objects. CVSS 3.1 Base Score 8.1 (Confidentiality, Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H).

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Oracle Peoplesoft Enterprise Cc Common Application Objects.

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

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

## Is CVE-2026-61307 being exploited?

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

## Other vulnerabilities in Oracle Corporation PeopleSoft Enterprise CC Common Application Objects

- [CVE-2026-60606](https://insights.sbomify.com/CVE-2026-60606/): Missing authorization in PeopleSoft Enterprise CC Common Application Objects (critical 9.1)
- [CVE-2026-61078](https://insights.sbomify.com/CVE-2026-61078/): Open redirect in PeopleSoft Enterprise CC Common Application Objects (high 8.7)
- [CVE-2025-30735](https://insights.sbomify.com/CVE-2025-30735/): Missing authorization in PeopleSoft Enterprise CC Common Application Objects (high 8.1)
- [CVE-2025-21562](https://insights.sbomify.com/CVE-2025-21562/): Missing authorization in PeopleSoft Enterprise CC Common Application Objects (medium 4.3)
- [CVE-2025-21563](https://insights.sbomify.com/CVE-2025-21563/): Missing authorization in PeopleSoft Enterprise CC Common Application Objects (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-61307 is a high-severity authentication bypass vulnerability in Oracle Corporation PeopleSoft Enterprise CC Common Application Objects, published on 18 Aug 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-61307 in the wild and no public exploit code.

Affected product: Oracle Corporation PeopleSoft Enterprise CC Common Application Objects. 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-61307/ (Markdown: https://insights.sbomify.com/CVE-2026-61307/index.md)
```

## Sources

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

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