# CVE-2026-62479: Missing authorization in Oracle Public Sector Financials

> Low-privileged attackers can modify or read data in Oracle Public Sector Financials via HTTP with user interaction.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 22 Jul 2026
- **Also known as:** GHSA-782x-53q3-wrhf

## What is CVE-2026-62479?

CVE-2026-62479 is a medium-severity missing authorization vulnerability in Oracle Public Sector Financials, published on 21 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Vulnerability in the Oracle Public Sector Financials product of Oracle E-Business Suite (component: Internal Operations).  Supported versions that are affected are 12.2.3-12.2.15. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Public Sector Financials.  Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Public Sector Financials, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in  unauthorized update, insert or delete access to some of Oracle Public Sector Financials accessible data as well as  unauthorized read access to a subset of Oracle Public Sector Financials accessible data. CVSS 3.1 Base Score 5.4 (Confidentiality and Integrity impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N).

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Oracle Public Sector Financials.

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

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

## Is CVE-2026-62479 being exploited?

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

## Other vulnerabilities in Oracle Public Sector Financials

- [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-46823](https://insights.sbomify.com/CVE-2026-46823/): Missing authorization in Oracle Public Sector Financials (International) (high 7.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-62479 is a medium-severity missing authorization vulnerability in Oracle Public Sector Financials, published on 21 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-62479 in the wild and no public exploit code.

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

## Sources

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

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