# CVE-2026-83160: Privilege escalation in Oracle Database Server

> A low-privileged attacker with Create Table privileges can compromise the Oracle Database RDBMS via network access, leading to full takeover.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-rw58-ggjw-fq25

## What is CVE-2026-83160?

CVE-2026-83160 is a high-severity vulnerability in Oracle Database Server, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vulnerability in the RDBMS component of Oracle Database Server.  Supported versions that are affected are 23.4.0-23.26.3. Easily exploitable vulnerability allows low privileged attacker having Create Table privilege with network access via Oracle Net to compromise RDBMS.  Successful attacks of this vulnerability can result in takeover of RDBMS. CVSS 3.1 Base Score 8.8 (Confidentiality, Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-83160 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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