# CVE-2026-83080: Auth bypass in Oracle Banking Branch

> A low-privileged attacker can compromise Oracle Banking Branch via HTTP with user interaction, leading to full system takeover.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 15 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-477g-r25c-hrmc

## What is CVE-2026-83080?

CVE-2026-83080 is a high-severity authentication bypass vulnerability in Oracle Banking Branch, published on 15 Sep 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 Banking Branch product of Oracle Financial Services Applications (component: Reports).  Supported versions that are affected are 14.5.0.0.0-14.9.0.0.0. Difficult to exploit vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Banking Branch.  Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of Oracle Banking Branch. CVSS 3.1 Base Score 7.1 (Confidentiality, Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H).

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-83080 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-83080 is a high-severity authentication bypass vulnerability in Oracle Banking Branch, published on 15 Sep 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-83080 in the wild and no public exploit code.

Affected product: Oracle Banking Branch. 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-83080/ (Markdown: https://insights.sbomify.com/CVE-2026-83080/index.md)
```

## Sources

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

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