A low-privilege login can take over Oracle Text
Oracle rates CVE-2026-114848 critical at 9.9. An account with CREATE SESSION can take control of Oracle Text over Oracle Net on affected database releases.
Reviewed by Codex · 18 November 2026

The privilege Oracle names for CVE-2026-114848 is one that database users ordinarily need just to log in. On 17 November 2026, Oracle disclosed that a user with CREATE SESSION who can connect over Oracle Net can take control of Oracle Text on affected releases. Oracle included the fix in its November Critical Security Patch Update and credited Nam Nguyen of VinSOC, working with Trend Micro’s Zero Day Initiative. Oracle’s November advisory
What a takeover puts within reach
Oracle Text is the full-text search component inside Oracle Database. An application might use it to find a phrase in thousands of contracts, then use ordinary SQL to narrow the matches to a single customer. The text index lives in the database, and the database process runs the query. The documents it indexes can also come from files or the web. Oracle Database Concepts
Oracle rates the flaw 9.9 out of 10 under CVSS 3.1. It assesses attack complexity as low and says exploitation requires no action by another user. Oracle assigns high impact to confidentiality, integrity and availability. Its stated outcome is takeover of Oracle Text. The advisory also flags a possible impact on other products, without specifying which ones or establishing that an attacker gains administrative control of the host. Oracle’s description of CVE-2026-114848
Which database releases need the fix?
Oracle lists three affected ranges of supported Database Server releases. Both endpoints of each range are included. Oracle Database Server risk matrix
- 19c — 19.3 through 19.33
- 21c — 21.3 through 21.24
- 23 release line — 23.4.0 through 23.26.3
There is an easy mistake to make on 19c. A second Oracle Text flaw in the same bulletin, CVE-2026-114819, also scores 9.9, and its affected range stops at 19.32. A database on 19.33 still falls within the range for CVE-2026-114848. Match the patch record to the full CVE identifier. Oracle risk matrix entries for both flaws
Where to start the patch review
Ask the database owner for the running release and the component inventory. Oracle’s DBA_REGISTRY view records the components loaded into a database, their versions and their status. Include databases used only by internal applications. An application server with a route to Oracle Net and a service account with CREATE SESSION can meet the access conditions even when the database has no public address. Oracle component registry · Access conditions
For each affected installation, use the November patch availability document linked from Oracle’s advisory, My Oracle Support note CPU454, to select the patch for that release and platform. For a managed database, ask the provider which patch covers this CVE and when it was applied to your instance. Oracle patch information
What counts as a verified fix?
Record the patch ID and confirm it in the Oracle home the database actually uses. If the patch requires SQL changes, check their outcome in each applicable database. Oracle’s DBA_REGISTRY_SQLPATCH records both applications and rollbacks. Check the latest action for the relevant patch ID. A successful rollback means the patch was removed, even though the row says SUCCESS. Then run an ordinary application search to confirm that the index still serves results. Oracle SQL patch registry