On this page (7 sections)
CVE-2026-114819 is a critical vulnerability in the Oracle Text component of Oracle Database Server. It was published in the National Vulnerability Database on 2026-11-17 with a CVSS 3.1 base score of 9.9, and it affects the 19c, 21c and 23 release lines within the version ranges listed below.
If you run an Oracle database that backs a website, store or internal application, you should find out whether Oracle Text is installed and read Oracle's advisory today. The public record is short, so this article separates what is confirmed from what is not.
What was disclosed
The NVD record describes an easily exploitable vulnerability in Oracle Text. A low privileged attacker who holds the Create Session privilege and has network access via Oracle Net can compromise Oracle Text. Successful attacks can result in takeover of Oracle Text.
The description also notes a scope change: although the flaw is in Oracle Text, attacks may significantly impact additional products.
The GitHub Advisory Database entry (GHSA-6vhq-xvx6-gpf7) carries the same description as the NVD record. It is marked unreviewed and lists no package, no patched versions and no CWE. Both records reference an Oracle security alert page, which we did not retrieve, so we cannot say what it contains. The NVD and GitHub texts are the same description, not two independent confirmations, and only one independent publisher covers this story so far.
Reading the CVSS score
The vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. In plain terms:
- Attack vector network: the attacker does not need local access to the server.
- Attack complexity low: no special conditions are described.
- Privileges required low: the description names a low privileged account with the Create Session privilege.
- User interaction none: no one has to click anything.
- Scope changed: impact can extend beyond Oracle Text.
- Confidentiality, integrity and availability all high.
Who is exposed
Exposure depends on three things: whether your Oracle Database Server version falls inside the affected ranges, whether Oracle Text is part of your installation, and who can reach the listener over Oracle Net. The sources do not say whether Oracle Text must be actively used to be vulnerable, so do not assume an unused installation is safe. Confirm with Oracle's advisory.
Because the attacker needs only a low privileged account, it is worth checking which accounts can log in. Application and reporting accounts may hold Create Session, so check yours. A stolen database credential, or a separate flaw in an application that connects to the database, could in principle supply that starting position. That is a general risk observation, not something the sources report as happening.
| Release line | Affected versions |
|---|---|
| 19c | 19.3-19.32 |
| 21c | 21.3-21.24 |
| 23 | 23.4.0-23.26.3 |
How to check your exposure
Start with a read-only check of your database version. Run this in SQL*Plus or another SQL client as a user allowed to query the view; it returns the version banner so you can compare it with the ranges above.
SELECT banner_full FROM v$version;If your release does not return banner_full, the plain banner column in the same view works on older releases. Next, check whether Oracle Text is installed. This query lists the component registry entries; look for a row named Oracle Text and note its status.
SELECT comp_name, version, status FROM dba_registry WHERE comp_name LIKE '%Text%';Then list which accounts hold Create Session directly. This query returns the grantee names; review each one. Also ask your network team whether access to Oracle Net is limited to application servers and administrators.
SELECT grantee FROM dba_sys_privs WHERE privilege = 'CREATE SESSION' ORDER BY grantee;What to do now
Given the 9.9 score, treat this as urgent. The sources we reviewed do not confirm that a patch or fixed version exists, so the first task is to learn from Oracle what is available for your release.
- Read Oracle's advisory at the cspunov2026 page referenced by the CVE record and confirm whether a patch or mitigation is available for your release line.
- Inventory every Oracle Database Server instance and record its exact version against the 19.3-19.32, 21.3-21.24 and 23.4.0-23.26.3 ranges.
- Check whether Oracle Text is installed on each instance and note it in your inventory.
- If Oracle provides a patch for your release, test it on a non-production copy first, then roll it out to production in a maintenance window, prioritized urgently.
- Restrict Oracle Net access to known application and admin hosts using firewall or listener controls, and do not expose the listener to the internet.
- Review accounts with Create Session. Remove or lock accounts that are unused, and rotate credentials for shared or application accounts you cannot vouch for.
- Review database and application logs for unexpected logins or new objects created by low-privileged accounts since the record was published on 2026-11-17.
Detection and monitoring afterwards
The sources say nothing about indicators of compromise, so there is no known signature to hunt for. Reasonable general monitoring is to watch for logins from unfamiliar hosts, unusual activity by low-privileged accounts, and changes to Oracle Text objects or other database components. Keep database audit logs where an attacker with a compromised account cannot erase them.
If a website sits in front of the database, Webforta Scan can check the public side of that site, and Webforta Monitor can alert you to uptime, certificate and DNS changes. Neither can see inside a database or confirm whether this flaw is present, so version checks on the server remain essential. For wider background, see Small business website security.
What we do not know yet
- Fixed versions or patch identifiers: not given in the sources we reviewed.
- Whether the flaw is being exploited: no report in the sources, and no CISA KEV entry in the record.
- The weakness class and technical mechanism: not published in these records.
- Whether Oracle Text must be enabled or in use for an instance to be affected: not stated.
- What Oracle's own advisory page says: we did not retrieve it.
We will treat these as open until Oracle's advisory or other primary sources answer them.
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.
