On this page (7 sections)
CVE-2026-114850 is a critical vulnerability in the General component of Oracle APEX. According to the NVD record, an unauthenticated attacker with network access over HTTPS can exploit it, and a successful attack can result in takeover of Oracle APEX. The record carries a CVSS 3.1 base score of 9.8.
A second record, CVE-2026-114849, has the same description, the same score and the same list of affected versions. If you run Oracle APEX on a server reachable from the internet, treat both as one patching task and check Oracle's alert for the fix.
What was published
The record was published by the National Vulnerability Database on November 17, 2026, and appeared in the GitHub Advisory Database the next day as GHSA-2775-w35j-r3hp. The GitHub entry is marked unreviewed and lists no package, no affected-version range and no patched version, so it adds nothing beyond the NVD text. Both records point to Oracle's security alert page as a reference.
Only one independent publisher covers this story so far, and the NVD pages repeat the same underlying description. That means the details below rest on a single description, not on several confirmations.
What the score tells you
The CVSS vector is worth reading, because it explains why this is rated critical:
- Attack vector: network. The attacker does not need local or adjacent access.
- Attack complexity: low. The record calls it easily exploitable.
- Privileges required: none, and no user interaction. No login and no victim click are needed.
- Confidentiality, integrity and availability: all high. The description says a successful attack can result in takeover of Oracle APEX.
In plain terms, this is the profile of a flaw that can be attacked remotely against an exposed service without any credentials. The research does not name the weakness class (the CWE field is empty), and it does not describe the mechanism, the affected endpoint or the conditions needed. Anything beyond the description above would be guesswork, so this article does not speculate.
Who is realistically exposed
The record names four version strings as affected: 24.1.22, 24.2.21, 26.1.5 and 26.2.0. The wording says supported versions that are affected, so a release line you run that is not on this list is not necessarily safe or unsafe; the research does not say. Check Oracle's alert for the exact scope.
The attack path described is network access over HTTPS with no authentication, so exposure is highest where APEX is reachable from the internet. Deployments reachable only from internal networks are lower risk from remote attackers, but the research does not say they are unaffected, so inventory and patch those too.
How to check your exposure
First find out whether you run APEX at all, and which version. Your APEX or database administrator can confirm the installed version from your own deployment records or Oracle's documentation. Compare what you find with the four affected version strings above.
Next, work out who can reach it. List the hostnames and reverse proxies that publish APEX applications and confirm whether each one is open to the internet. Reviewing your public hostnames can help you spot forgotten endpoints; the free SSL certificate checker is one way to see what a public hostname presents.
What to do now
- Inventory every Oracle APEX instance, including development, test and forgotten ones, and record each version.
- Open Oracle's security alert and find the fix or patch instructions for your version. The research does not state a fixed version, so rely on Oracle's page.
- Schedule the update as an urgent change for any instance reachable from the internet, and apply it first there.
- Until you can patch, restrict network access to APEX to trusted addresses at the firewall, load balancer or reverse proxy.
- Take a backup of the APEX workspace and its database before changing anything, so you can recover if the update goes wrong.
- Review web server and database logs for the period since November 17, 2026 for unexpected requests, new accounts, changed applications or unfamiliar administrative activity.
- Treat CVE-2026-114849 as part of the same task and confirm Oracle's guidance covers both.
Detection and monitoring afterwards
The research gives no indicators of compromise and no sign of exploitation in the wild, so there is no signature to hunt for. A sensible approach is to look for general signs of takeover: new or modified APEX users and workspaces, changed application code, unexpected database objects, and outbound connections from the APEX host that you do not recognize.
Keep watching Oracle's page and the NVD entries for updates. If exploitation is later confirmed, or the record is revised with a fixed version or weakness class, the priority of your response may change. For ongoing visibility of certificate, DNS and uptime changes on the hostnames that front your APEX applications, Webforta Monitor can alert you to changes; it does not detect or block this vulnerability. For broader habits that cut exposure across all your systems, see our small business website security guide.
What we do not know yet
- The fixed version or patch identifier is not stated in the research.
- The weakness type (CWE) is not assigned in the record.
- There is no confirmed report of exploitation and no public proof of concept in the research.
- The GitHub advisories are unreviewed and list affected and patched versions as unknown.
- Why two CVE records share an identical description is not explained.
We will treat the details above as provisional until Oracle's alert or further research adds more.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
