A critical, easily exploitable flaw in the General component of Oracle APEX lets an unauthenticated attacker with network access over HTTPS take over the application.
What Is It
CVE-2026-114850 is a vulnerability in the General component of Oracle APEX. Oracle reported it, and NVD published it on November 17, 2026. NVD says an unauthenticated attacker with network access via HTTPS can easily exploit it to compromise Oracle APEX. A successful attack can result in takeover of Oracle APEX.
The weakness is classified as CWE-306 (Missing Authentication for Critical Function). Oracle scores it CVSS 3.1 9.8 (Critical) with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. That vector means:
- It is exploitable over the network.
- Attack complexity is low.
- No privileges or user interaction are required.
- Confidentiality, integrity and availability impacts are all high.
Why It Matters
This is the profile defenders worry about most: it is remotely reachable, needs no credentials and can lead to takeover of the application. CISA's SSVC assessment in the NVD record rates the flaw:
- Automatable: yes
- Technical impact: total
- Exploitation: none
At the time of the assessment, CISA's SSVC rating recorded no evidence of exploitation. CVE-2026-114850 is not listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, so KEV does not confirm active exploitation. Because the flaw is automatable and needs no authentication, internet-facing APEX instances should still be a priority to patch.
The NVD record is in "Received" status, which means NVD has not yet completed its own analysis. The current score and details come from Oracle as the CNA.
What's Vulnerable
Oracle lists these supported versions of Oracle APEX as affected:
- 24.1.22
- 24.2.21
- 26.1.5
- 26.2.0
The NVD record does not yet list any CPE entries.
Patch Status
Because the flaw is not in KEV, there is no CISA-mandated required action or due date. The NVD record links to an Oracle security alert advisory for vendor remediation guidance. The available data does not name specific fixed versions. Administrators running any of the affected APEX versions should:
- Read Oracle's advisory and apply the fix it provides.
- Restrict network exposure of APEX endpoints until the fix is applied.