On this page (7 sections)
CVE-2026-114848 is a critical vulnerability in the Oracle Text component of Oracle Database Server. According to the NVD record and the GitHub Advisory Database entry, an attacker with only a low-privileged database account and network access via Oracle Net can take over Oracle Text, and the impact can reach beyond it.
If you run Oracle Database Server in the affected version ranges (including databases behind web applications, stores or internal portals), this is one to review today. The details below stick to what the published records say, and flag clearly what they do not.
What was disclosed
The record describes an easily exploitable flaw in Oracle Text. A low-privileged attacker who holds the Create Session privilege and can reach the database over Oracle Net can compromise Oracle Text. Successful attacks can result in takeover of Oracle Text.
The record also notes a scope change: although the weakness is in Oracle Text, attacks may significantly impact additional products. That is why the score is 9.9 even though some privileges are required. The vendor's reference is the Oracle security alert, listed in both records.
Understanding the severity score
The published 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, only a path to the database over Oracle Net.
- Attack complexity Low and user interaction None: no special conditions and no victim has to click anything.
- Privileges required Low: a valid account with Create Session is enough. No administrator rights are needed.
- Scope Changed: a compromise of Oracle Text can affect resources beyond it.
- Confidentiality, integrity and availability all High.
The practical meaning is that any account able to log in is a potential starting point, for example application accounts, reporting users, or stolen or reused credentials. The records do not say how the flaw is triggered, and we do not speculate about it here.
Who is realistically exposed
You are in scope if you run Oracle Database Server in any of these ranges, as listed in the CVE record:
| Release line | Affected versions |
|---|---|
| 19.x | 19.3 through 19.33 |
| 21.x | 21.3 through 21.24 |
| 23.x | 23.4.0 through 23.26.3 |
Exposure is highest where the Oracle listener is reachable from untrusted networks, where many accounts hold Create Session, or where applications share a database account with broad access. Databases reachable only from a tightly controlled application tier are lower risk, but not risk-free, because the precondition is just a working login.
How to check your exposure
Start by confirming exactly which version and patch level each database is on. This read-only query, run in SQL*Plus or SQL Developer as a privileged user, shows the database version banner:
SELECT banner FROM v$version;Compare the result with the affected ranges above. Then check whether Oracle Text is installed. This read-only query lists the component registry entry if it is present:
SELECT comp_id, comp_name, version, status FROM dba_registry WHERE comp_id = 'CONTEXT';A row with the status VALID indicates Oracle Text is installed. Finally, review who can log in. This lists accounts holding the CREATE SESSION privilege directly, which helps you see how wide the precondition is:
SELECT grantee FROM dba_sys_privs WHERE privilege = 'CREATE SESSION' ORDER BY grantee;What to do now
- Inventory every Oracle Database instance and record its exact version and patch level.
- Read the Oracle security alert for the patch or fix that applies to your release line and the fixed versions, which the public records here do not list.
- Schedule and apply the Oracle-provided update to affected databases, starting with those reachable from the internet or from large user populations.
- Restrict network access to the Oracle listener so only known application servers and admin hosts can connect.
- Audit accounts with Create Session. Disable unused accounts, rotate shared or old passwords, and remove the privilege where it is not needed.
- If Oracle Text is not used by any application, ask your Oracle support contact or the alert whether removing or restricting it is supported, rather than dropping components on your own.
- Review application database accounts for least privilege so a single compromised login exposes as little as possible.
Detection and monitoring
The sources give no indicators of compromise and do not report active exploitation, so there is no known signature to hunt for. Sensible general monitoring still applies while you patch:
- Enable and review database auditing for new sessions, failed logins and privilege changes, especially for low-privileged accounts.
- Watch listener logs for connections from unexpected source addresses.
- Alert on new or changed objects in the CTXSYS schema and on unexpected grants.
- Track unusual outbound connections from the database host.
If your databases back a public website, also keep an eye on the web tier. A free scan of your site and monitoring for certificate, DNS and header changes will not see inside Oracle, but they help you notice unexpected changes on the public side while you work through the database patching. For background on reducing exposure, see our small business website security guide.
Timeline
| Date | Event |
|---|---|
| 2026-11-17 | Record published by the National Vulnerability Database |
| 2026-11-18 | Entry added to the GitHub Advisory Database (marked Unreviewed) |
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.
