Introduction
Oracle has disclosed a Critical flaw in Oracle APEX that lets an unauthenticated attacker with nothing more than HTTPS network access potentially take over the APEX instance. Because APEX runs inside Oracle Database and ships with supported database editions, many internal business applications built on it may sit on systems that teams do not track as a distinct product.
Oracle APEX is an enterprise low-code application development platform built on Oracle Database, available both on premises and in Oracle's cloud. It is a fully supported feature included at no additional cost with supported database editions, with no separate APEX license fee. Oracle supports APEX, Oracle REST Data Services (ORDS) and Oracle Database as a stack. Oracle reports that APEX received a 2022 Gartner Peer Insights Customers' Choice distinction for Enterprise Low Code Application Platforms. That distinction reflects aggregated end-user opinion, and no current market share figure is available in the sources we reviewed.
Technical information
What Oracle has disclosed
CVE-2026-114850 resides in the General component of Oracle APEX. Oracle describes it as easily exploitable by an unauthenticated attacker with network access via HTTPS, and states that successful attacks can result in takeover of Oracle APEX. The published vector is:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Broken down:
- AV:N: network attack vector
- AC:L: low attack complexity
- PR:N: no privileges required
- UI:N: no user interaction
- S:U: scope unchanged
- C:H / I:H / A:H: High confidentiality, integrity and availability impact
The 9.8 score is Oracle's assessment as the CNA. NVD displays Oracle's score while its own assessment is not yet provided. As FIRST's CVSS v3.1 specification notes, Base metrics describe intrinsic severity. Exploit maturity and observed exploitation are separate questions.
The same APEX risk matrix in the November 2026 CSPU lists a second issue, CVE-2026-114849, also unauthenticated, reachable over HTTPS, and rated 9.8 with the identical vector.
Root cause: not publicly disclosed
The public record identifies the component and attack conditions, but not the vulnerable function, request format, parameter, payload or exploit sequence. NVD lists no CWE, and nothing we reviewed establishes whether the flaw is injection, memory corruption, an authorization failure or another weakness class. Oracle states that it does not disclose detailed vulnerability security analysis.
The fix is tracked internally as Oracle Bug 40129456, which appears in the APEX Known Issues pages under the deliberately generic title "Fix for bug 40129456". Oracle often uses titles like this so that bug lists do not reveal root cause, and Oracle does not publish source diffs or commits for APEX. As a result, no vulnerable code is publicly available, and we do not reproduce or reconstruct any here.
Where the vulnerable code runs
Oracle documents a three-tier architecture: browser requests pass through a web server to the database. In the documented request flow, ORDS passes the request to Oracle Database, APEX processes it inside the database, and the response returns through ORDS to the browser. APEX stores application metadata in database tables, reads that metadata when rendering pages or processing submissions, and executes PL/SQL against database schemas.
This explains why an APEX flaw reached over HTTPS is relevant to database-hosted applications. It does not identify the vulnerable endpoint, and it does not show that this CVE compromises ORDS, the database engine or the underlying host. With scope unchanged, the documented impact is takeover of APEX itself. The advisory does not support claims of operating system or database administrator compromise.
Attack flow based on public data
Given what Oracle has published, the supportable attack flow is limited to the following:
- The attacker has network access to an APEX deployment over HTTPS, which in Oracle's documented architecture reaches APEX through ORDS.
- The attacker sends requests that reach the vulnerable code in the General component. No credentials, session or victim interaction are required.
- Low attack complexity means no special conditions outside the attacker's control are needed.
- Successful exploitation can result in takeover of Oracle APEX, with High impact to confidentiality, integrity and availability within that scope.
Application-level authentication in front of APEX applications should not be treated as a barrier here, since the vulnerability requires no privileges.
Exploitation status
The reviewed sources do not establish active exploitation of CVE-2026-114850, a verified public exploit, or any named threat actor. The CVE description says exploitation is possible, not that it has been observed. The CISA KEV catalog content we reviewed did not show an entry for this CVE, though that view was not sufficient to prove absence. Oracle credits Ikotas Labs working with Trend Micro's Zero Day Initiative for reporting the issue. That credit acknowledges the disclosure and does not identify an attacker. Exploitation is therefore unconfirmed: it has been neither observed nor ruled out.
Patch information
Oracle fixed CVE-2026-114850 in its November 2026 Critical Security Patch Update (CSPU), released November 17, 2026 (Rev 1). Oracle's CSAF document for this CSPU (cspunov2026csaf.json) marks the remediation as a vendor_fix available to Oracle customers with valid support contracts, and maps the CVE to Oracle Bug 40129456 (Oracle APEX).
Fixed patch levels
The fix ships inside the regular cumulative Patch Set Bundle (PSE) for each supported release line. Bug 40129456 appears in all four lines:
- 24.1: affected 24.1.22; PSE (MOS patch ID) 36695709; fixed at 24.1.23 (Patch Version 23)
- 24.2: affected 24.2.21; PSE 37366599; fixed at 24.2.22 (Patch Version 22)
- 26.1: affected 26.1.5; PSE 39179920; fixed at 26.1.6 (Patch Version 6)
- 26.2: affected 26.2.0; PSE 40040466; fixed at 26.2.1 (first PSE for 26.2)
Each affected level is exactly one patch level below the fixed one. Systems that were current as of the previous bundle remain vulnerable. Only the newest bundle in each line closes the issue. The CSAF vendor_fix entry is attached to the affected product IDs (24.1.22, 24.2.21, 26.1.5, 26.2.0), which means a fix exists for those builds. Those numbers are not fixed versions.
What else is in the bundle
The PSEs are cumulative maintenance bundles. On 26.2, for example, PSE 40040466 also contains other opaque entries (bugs 40121974, 40101548 and 40173496), functional fixes, and a hardening change, Bug 40055514, addressing a Content Security Policy header missing from APEX AJAX responses. Oracle does not say whether any of these relate to CVE-2026-114850, so the only authoritative fix marker is Bug 40129456.
Timing
The Known Issues pages show all four bundles were last updated around November 4, 2026, roughly two weeks before the CSPU disclosed the CVE. A bundle downloaded from My Oracle Support after that refresh likely already contains the fix, but verify by patch level rather than by download date.
Obtaining and verifying the fix
- Download the bundle from My Oracle Support (Patches & Updates, then search the patch ID). For example:
https://support.oracle.com/epmos/faces/PatchDetail?patchId=40040466
- Oracle's database patch availability document for this CSPU is CPU431. A support contract is required.
- Oracle states the bundles can be reapplied as needed. If you installed an older copy of the same PSE, reapplying the refreshed bundle moves you to the fixed patch level.
- After patching, confirm the installed
PATCH_VERSIONis at least the fixed value listed above. - If your deployment loads APEX static resources from Oracle's CDN, point it to the CDN paths published on the Known Issues pages for the new patch level.
Autonomous Database
On Autonomous Database, Oracle documents that APEX Patch Set Bundles are applied automatically during scheduled database maintenance when the Dictionary component is patched. That describes general service behavior and does not confirm that a particular environment has received this fix, so check the patch level. Oracle also documents cloning a database, applying a new APEX release to the clone and testing applications before upgrading production.
Temporary controls and their limits
Oracle lists blocking the network protocol required by an attack, here HTTPS, as a possible temporary risk reduction. Oracle also warns that this may break application functionality, recommends testing outside production, and states it does not correct the underlying problem. Oracle's separate guidance on removing privileges or package access does not apply, because this vulnerability requires no privileges. CSPUs are not cumulative, while CPUs are cumulative as much as possible. Applying this update does not resolve previously skipped updates.
Affected systems and versions
Oracle lists the following supported versions of Oracle APEX (component: General) as affected:
- 24.1.22
- 24.2.21
- 26.1.5
- 26.2.0
Any of these builds reachable over HTTPS is in scope, and no authentication, privileges or user interaction are required. Oracle notes that unsupported releases are not tested and that earlier versions of affected releases may also be vulnerable, so absence from the list does not establish safety. Oracle recommends remaining on actively supported versions.
Vendor security history
Oracle's published process combines quarterly Critical Patch Updates, targeted Critical Security Patch Updates between quarterly releases, and Security Alerts for issues too urgent to wait. Oracle can also ship patches or workarounds outside its normal schedule for particularly critical vulnerabilities or reported active exploitation.
A separate and unrelated incident shows that exploitation of Oracle enterprise software has occurred. The UK NCSC confirmed active exploitation of CVE-2025-61882 in Oracle EBS, describing unauthenticated crafted HTTP requests that could result in full system compromise. Google Threat Intelligence Group and Mandiant documented an extortion campaign claiming CL0P affiliation, possible exploitation before patch availability, and data exfiltration in some cases. Oracle directed customers to emergency patches on October 4, 2025. GTIG reported overlaps with FIN11-related activity but did not formally attribute the campaign, noting CL0P branding is not exclusive to FIN11.
That case involves a different product and a different vulnerability. It does not establish APEX exploitation, a shared root cause or shared attackers, and its indicators should not be relabeled as APEX indicators.
References
- NVD vulnerability detail for CVE-2026-114850
- CVE.org record for CVE-2026-114850
- Oracle Critical Security Patch Update Advisory, November 2026
- Text form of Oracle CSPU November 2026 risk matrices
- Oracle CSAF document for the November 2026 CSPU
- Oracle APEX 24.1 Known Issues
- Oracle APEX 24.2 Known Issues
- Oracle APEX 26.1 Known Issues
- Oracle APEX 26.2 Known Issues
- VulDB entry
- Oracle APEX architecture
- Oracle APEX product page
- Oracle APEX blog: 2022 Gartner Peer Insights recognition
- Oracle Security Fixing Policies
- Oracle Critical Patch Update and Security Alert FAQ
- FIRST CVSS v3.1 Specification
- Oracle APEX 26.2 Installation Guide
- Control Oracle APEX Upgrades on Autonomous Database
- CISA Known Exploited Vulnerabilities Catalog
- UK NCSC: Active exploitation of vulnerability affecting Oracle EBS
- Google Threat Intelligence: Oracle EBS zero day exploited in extortion campaign



