Introduction
Oracle's November 2026 Critical Security Patch Update fixes an Oracle APEX flaw that, according to Oracle, lets an unauthenticated attacker with HTTPS access take over the APEX instance. The issue carries a CVSS 3.1 score of 9.8 and needs no credentials or user interaction. Oracle's record also lists Oracle REST Data Services (ORDS) as an affected product, which widens the set of components teams need to patch.
Oracle APEX is a low-code platform from Oracle Corporation for building applications, including mission-critical ones, and it is available at no additional cost with Oracle Autonomous AI Database and other Oracle AI Database distributions. Oracle documents cloud, on-premises, hybrid and multicloud deployments, and Nucleus Research placed APEX among the Leaders in its 2025 LCAP Technology Value Matrix. Oracle also reports customer outcomes such as Nomura Research Institute cutting application development effort by 65% after adopting APEX, which shows that APEX frequently hosts production business applications rather than only internal prototypes.
Technical information
What Oracle has disclosed
Oracle identifies the affected product as Oracle APEX and the component only as General. NVD shows no CWE classification for this record, and the 9.8 Critical score shown on NVD is attributed to Oracle as the CNA rather than an independent NIST assessment. Oracle states that it does not publish its detailed vulnerability analysis.
That means the root cause is not public. The vulnerable endpoint, request parameters, payload, internal function and any prerequisite configuration have not been disclosed. In our reading of the sources, there is no basis for labeling this as SQL injection, deserialization or any other specific weakness class, and we have not done so here.
What the CVSS vector tells us
The published vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H:
- Attack Vector: Network. Remotely reachable. Oracle specifies HTTPS as the protocol.
- Attack Complexity: Low. Oracle rates exploitation as easy.
- Privileges Required: None. No authenticated APEX account is needed.
- User Interaction: None. No other user has to click or visit anything.
- Scope: Unchanged. The score does not assert a change of security authority.
- Confidentiality, Integrity, Availability: High. Successful attacks result in takeover of Oracle APEX.
These metrics describe potential severity and access conditions. They do not reveal the defect itself, and they do not indicate that exploitation has occurred.
Why ORDS is in scope
Oracle's CVE record lists two affected products: Oracle APEX and Oracle REST Data Services 24.2.0 through 26.3.0. ORDS is explicitly marked as affected, not just mentioned as a dependency.
APEX does not serve HTTP traffic itself. ORDS is the Java web tier that sits in front of APEX and handles incoming HTTPS requests. Because both products are listed under one CVE, a fully remediated deployment needs updated APEX code in the database and an updated ORDS listener. The APEX description does not explain the specific ORDS exploitation path, so we would not assume the two share an identical exploit procedure.
Attack flow based on the published conditions
Working only from what Oracle has published, the attack sequence looks like this:
- The attacker has network access to an APEX deployment over HTTPS, which in a standard deployment means reaching the ORDS web tier in front of APEX.
- The attacker does not need an APEX account and does not need any user to interact with the request.
- The attacker triggers the undisclosed flaw in the General component. Oracle rates this as low complexity, but the specific requests and payloads are not public.
- Successful exploitation results in takeover of Oracle APEX, with high confidentiality, integrity and availability impact.
The disclosure does not establish operating-system-level compromise, a specific injection technique, or unrestricted compromise of every connected database. Those outcomes should not be inferred from the takeover description.
Why built-in APEX controls are not a workaround
Oracle describes APEX security capabilities such as granular access controls, auditing and identity integration. This vulnerability does not require a legitimate account, so those controls are not evidence of a workaround. Similarly, Oracle's general advice about reducing unnecessary privileges applies to attacks that need privileges. This one does not, so changing user roles alone should not be expected to prevent exploitation.
Exploitation status
A contemporary SecurityOnline roundup of the November update names CVE-2026-114849 among the 9.8 APEX issues and reports no confirmed active exploitation across the update, adding that none of Oracle's new CVEs appear in CISA's KEV catalog. The CISA catalog material we reviewed (catalog version 2026.11.17) did not allow an exhaustive check, so KEV absence is not conclusively established. We found no named threat actor, campaign, verified public exploit or CVE-specific indicators of compromise.
Oracle credits an anonymous researcher working with Trend Micro's Zero Day Initiative; Connor Laidlaw and Matthew Keeley of Platform Security; Nam Nguyen, Thanh Vu and Tin Huynh of VinSOC; and Taisic Yun of Xint. These are vulnerability reporting credits, not attacker attribution.
Patch information
Oracle has an official fix. It ships in the Oracle Critical Security Patch Update (CSPU) for November 2026, released on 17 November 2026 (Rev 1, initial release). APEX and ORDS are closed source, so there is no public commit or code diff. The fix is only available as a vendor-built patch.
Where the fix appears
The CVE is listed in the Oracle APEX risk matrix of the November 2026 CSPU:
- CVE: CVE-2026-114849
- Product: Oracle APEX
- Component: General
- Protocol: HTTPS
- Remotely exploitable without authentication: Yes
- CVSS 3.1: 9.8
Oracle states that its risk matrices list only vulnerabilities newly addressed by the patches in that advisory, so this entry means the CSPU contains new code closing this specific flaw rather than a fix carried forward from an earlier cycle. In this release Oracle shipped 2 new security patches for APEX and 8 for ORDS.
Why both APEX and ORDS need patching
Because Oracle lists both APEX and ORDS under this CVE, a fully patched deployment needs updated APEX code in the database and an updated ORDS listener. Patching only one of them may leave the vulnerable path open.
The affected APEX versions are each the latest patch level of their release line (24.1, 24.2, 26.1, 26.2). In practice, no earlier patch bundle in any of these lines contains the fix, and the November 2026 CSPU deliverables are the first. Oracle's public advisory does not name exact fixed build numbers.
Oracle's APEX 24.2 Known Issues page gives a concrete example. It lists bundle patch 37366599, last updated September 30, 2026, with patch version 21. Applying it produces APEX 24.2.21, which the November advisory lists as affected. That bundle is useful for version tracking, but it is not the remediation for this CVE.
How to get the patch
For both APEX and ORDS, the advisory points to the Oracle Database Patch Availability Document (Document ID CPU431) on My Oracle Support. That document lists the specific patch numbers and download links for each supported release. Downloading the binaries requires a valid Oracle support contract, but anyone can confirm that the fix exists and where it is documented.
To confirm the installed APEX build, Oracle's APEX 24.2 documentation points to Help > About and the Product Build and Patch Version fields.
Delivery cadence and scheduling
- Oracle now releases security patches monthly on the third Tuesday, alternating the quarterly CPU with the monthly CSPU. Upcoming dates are 15 Dec 2026 (CSPU), 19 Jan 2027 (CPU), 16 Feb 2027 (CSPU) and 16 Mar 2027 (CSPU).
- Oracle's guidance is to stay on actively supported versions and apply CSPU patches without delay, testing them on non-production systems first.
- This is an unauthenticated, network-reachable issue scored 9.8 that can lead to full takeover of APEX, so it belongs in an emergency change window rather than the next routine maintenance cycle.
Oracle's general advisory guidance notes that blocking protocols required by an attack may reduce risk until patches are applied. For this CVE the protocol is HTTPS, and Oracle publishes no APEX-specific URL rule, WAF signature or configuration setting. Oracle also warns that such restrictions can break application functionality and do not correct the underlying problem, so they are not a substitute for the patch.
Affected systems and versions
Oracle APEX (component: General), supported versions listed as affected:
- 24.1.22
- 24.2.21
- 26.1.5
- 26.2.0
Oracle REST Data Services, listed as affected in the CVE record:
- 24.2.0 through 26.3.0
Versions are reproduced at the precision Oracle uses. Unlisted releases should not be treated as automatically safe, and unsupported releases should be moved to a supported version so the November fix can be applied.
Vendor security history
Oracle's July 2026 Critical Patch Update fixed two earlier APEX issues, both remotely exploitable without authentication:
- CVE-2026-54285, CVSS 5.3, protocol listed as multiple, low availability impact with no confidentiality or integrity impact. Affected APEX 24.2 and 26.1.
- CVE-2026-60156, CVSS 5.3, over HTTP, low confidentiality impact with no integrity or availability impact. Affected APEX 24.1, 24.2 and 26.1.
The November flaw shares the same unauthenticated entry condition but jumps to high impact across confidentiality, integrity and availability. Nothing in the sources suggests the July issues enabled this one.
Oracle's patch program includes quarterly Critical Patch Updates, out-of-schedule Security Alerts and, beginning June 2026, Critical Security Patch Updates on the third Tuesday of months between quarterly releases. November falls into that monthly program. The record shows an active remediation process alongside recurring APEX security fixes. The sources do not establish average response times or the discovery date of this defect.
References
- NVD: CVE-2026-114849
- NVD: CVE-2026-114849 (patch source link)
- CVE Record: CVE-2026-114849
- Oracle Critical Security Patch Update Advisory, November 2026
- Oracle Critical Security Patch Update Advisory, November 2026 (verbose)
- Oracle Critical Patch Update Advisory, July 2026
- Oracle Security Fixing Policies
- Oracle Security Vulnerability Remediation Practices
- Oracle APEX Downloads
- Oracle APEX 24.2 Known Issues
- Upgrading from a Previous APEX Release (26.2 docs)
- Oracle APEX Application Development
- Low Code, Oracle APEX
- Oracle: LCAP Technology Value Matrix 2025
- Nucleus Research: LCAP Technology Value Matrix 2025
- Nucleus Research: 2025 LCAP Technology Value Matrix release
- SecurityOnline: Oracle November 2026 Update Fixes 655 Flaws
- CISA Known Exploited Vulnerabilities Catalog
- CISA KEV JSON feed
- VulDB: CVE-2026-114849



