# CVE-2026-61233: Auth bypass in PeopleSoft Enterprise FIN Common Objects Brazil

> Unauthenticated attackers can compromise PeopleSoft Enterprise FIN Common Objects Brazil via HTTP, leading to full system takeover.

- **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:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 22 Jul 2026
- **Also known as:** GHSA-wrq9-xvch-r7w8

## What is CVE-2026-61233?

CVE-2026-61233 is a critical authentication bypass vulnerability in Oracle Corporation PeopleSoft Enterprise FIN Common Objects Brazil, 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 FIN Common Objects Brazil product of Oracle PeopleSoft (component: Integration).   The supported version that is affected is 9.1. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise PeopleSoft Enterprise FIN Common Objects Brazil.  Successful attacks of this vulnerability can result in takeover of PeopleSoft Enterprise FIN Common Objects Brazil. 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), CWE-287 (Improper Authentication), CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Oracle Peoplesoft Enterprise Fin Common Objects.

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

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

## Is CVE-2026-61233 being exploited?

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

## Other vulnerabilities in Oracle Corporation PeopleSoft Enterprise FIN Common Objects Brazil

- [CVE-2026-61237](https://insights.sbomify.com/CVE-2026-61237/): Auth bypass in PeopleSoft Enterprise FIN Common Objects Argentina (critical 9.9)
- [CVE-2026-61239](https://insights.sbomify.com/CVE-2026-61239/): Missing authorization in PeopleSoft Enterprise FIN Common Objects Argentina (critical 9.9)
- [CVE-2026-61242](https://insights.sbomify.com/CVE-2026-61242/): Auth bypass in PeopleSoft Enterprise FIN Common Objects Argentina (critical 9.9)
- [CVE-2026-61238](https://insights.sbomify.com/CVE-2026-61238/): Missing authorization in PeopleSoft Enterprise FIN Common Objects Argentina (critical 9.1)
- [CVE-2026-61243](https://insights.sbomify.com/CVE-2026-61243/): Auth bypass in PeopleSoft Enterprise FIN Common Objects Argentina (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-61233 is a critical authentication bypass vulnerability in Oracle Corporation PeopleSoft Enterprise FIN Common Objects Brazil, 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-61233 in the wild and no public exploit code.

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

## Sources

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

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