# CVE-2026-83268: Privilege escalation in Oracle BI Publisher

> High-privileged attackers can escalate privileges to fully compromise Oracle BI Publisher via network access, impacting confidentiality, integrity, and availability.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-6gvr-f32j-q7m9

## What is CVE-2026-83268?

CVE-2026-83268 is a critical vulnerability in Oracle BI Publisher, published on 15 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Vulnerability in the Oracle BI Publisher product of Oracle Analytics (component: BI Platform Security).  Supported versions that are affected are 8.2.0.0.0, 12.2.1.4.0 and  26.01.0.0.0. Easily exploitable vulnerability allows high privileged attacker with network access via HTTP to compromise Oracle BI Publisher.  While the vulnerability is in Oracle BI Publisher, attacks may significantly impact additional products (scope change).  Successful attacks of this vulnerability can result in takeover of Oracle BI Publisher. CVSS 3.1 Base Score 9.1 (Confidentiality, Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-83268 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-83268 is a critical vulnerability in Oracle BI Publisher, published on 15 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-83268 in the wild and no public exploit code.

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

## Sources

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

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