Oracle Database Server up to 19.31/21.22/23.26.2 JDBC privilege escalation

Summaryinfo

A vulnerability classified as very critical has been found in Oracle Database Server up to 19.31/21.22/23.26.2. Impacted is an unknown function of the component JDBC. Performing a manipulation results in privilege escalation. This vulnerability is reported as CVE-2026-47045. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability classified as very critical has been found in Oracle Database Server up to 19.31/21.22/23.26.2. This affects some unknown processing of the component JDBC. The manipulation with an unknown input leads to a privilege escalation vulnerability. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Vulnerability in the JDBC component of Oracle Database Server. Supported versions that are affected are 19.3-19.31, 21.3-21.22 and 23.4.0-23.26.2. Easily exploitable vulnerability allows high privileged attacker having None privilege with network access via Oracle Net to compromise JDBC. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of JDBC. CVSS 3.1 Base Score 6.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H).

The advisory is shared at oracle.com. This vulnerability is uniquely identified as CVE-2026-47045 since 05/18/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Additional levels of successful authentication are required for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 07/22/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Database Software

Vendor

• Oracle

Name

• Database Server

Version

• 19.0
• 19.1
• 19.2
• 19.3
• 19.4
• 19.5
• 19.6
• 19.7
• 19.8
• 19.9
• 19.10
• 19.11
• 19.12
• 19.13
• 19.14
• 19.15
• 19.16
• 19.17
• 19.18
• 19.19
• 19.20
• 19.21
• 19.22
• 19.23
• 19.24
• 19.25
• 19.26
• 19.27
• 19.28
• 19.29
• 19.30
• 19.31
• 21.0
• 21.1
• 21.2
• 21.3
• 21.4
• 21.5
• 21.6
• 21.7
• 21.8
• 21.9
• 21.10
• 21.11
• 21.12
• 21.13
• 21.14
• 21.15
• 21.16
• 21.17
• 21.18
• 21.19
• 21.20
• 21.21
• 21.22
• 23.26.0
• 23.26.1
• 23.26.2

License

• commercial

Website

• Vendor: https://www.oracle.com

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion