# CVE-2026-46823: Missing authorization in Oracle Public Sector Financials (International)

> Low-privileged attackers can bypass authorization controls to access critical data in Oracle Public Sector Financials via HTTPS.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 May 2026
- **Updated:** 29 May 2026
- **Also known as:** GHSA-m6mc-rc7h-2r2x

## What is CVE-2026-46823?

CVE-2026-46823 is a high-severity missing authorization vulnerability in Oracle Public Sector Financials (International), published on 28 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vulnerability in the Oracle Public Sector Financials (International) product of Oracle E-Business Suite (component: Authorization).  Supported versions that are affected are 12.2.6-12.2.15. Easily exploitable vulnerability allows low privileged attacker with network access via HTTPS to compromise Oracle Public Sector Financials (International).  While the vulnerability is in Oracle Public Sector Financials (International), attacks may significantly impact additional products (scope change).  Successful attacks of this vulnerability can result in  unauthorized access to critical data or complete access to all Oracle Public Sector Financials (International) accessible data. CVSS 3.1 Base Score 7.7 (Confidentiality impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N).

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Oracle Public Sector Financials.

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

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

## Is CVE-2026-46823 being exploited?

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

## Other vulnerabilities in Oracle Public Sector Financials (International)

- [CVE-2026-62478](https://insights.sbomify.com/CVE-2026-62478/): Auth bypass in Oracle Public Sector Financials (high 8.8)
- [CVE-2026-46967](https://insights.sbomify.com/CVE-2026-46967/): Auth bypass in Oracle Public Sector Financials (International) (high 8.8)
- [CVE-2021-2363](https://insights.sbomify.com/CVE-2021-2363/): Missing authorization in Public Sector Financials (International) (high 8.1)
- [CVE-2026-46923](https://insights.sbomify.com/CVE-2026-46923/): Auth bypass in Oracle Public Sector Financials (International) (high 8.0)
- [CVE-2026-60927](https://insights.sbomify.com/CVE-2026-60927/): Auth bypass in Oracle Public Sector Financials (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-46823 is a high-severity missing authorization vulnerability in Oracle Public Sector Financials (International), published on 28 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-46823 in the wild and no public exploit code.

Affected product: Oracle Public Sector Financials (International). 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-46823/ (Markdown: https://insights.sbomify.com/CVE-2026-46823/index.md)
```

## Sources

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

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