# CVE-2026-114850: Auth bypass in Oracle APEX

> Unauthenticated remote attackers can take over Oracle APEX due to missing authentication for a critical function.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-2775-w35j-r3hp

## What is CVE-2026-114850?

CVE-2026-114850 is a critical authentication bypass vulnerability in Oracle APEX, published on 17 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in Oracle APEX (component: General).  Supported versions that are affected are 24.1.22, 24.2.21, 26.1.5 and  26.2.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTPS to compromise Oracle APEX.  Successful attacks of this vulnerability can result in takeover of Oracle APEX. CVSS 3.1 Base Score 9.8 (Confidentiality, Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

An affected version is exposed as installed. No special setting or call is needed.


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

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

## Is CVE-2026-114850 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114850 is a critical authentication bypass vulnerability in Oracle APEX, published on 17 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-114850 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

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

## Sources

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

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