Oracle Database Server up to 19.31/21.22/23.26.2 Java VM improper authorization

Summaryinfo

A vulnerability classified as problematic has been found in Oracle Database Server up to 19.31/21.22/23.26.2. This issue affects some unknown processing of the component Java VM. This manipulation causes improper authorization. This vulnerability is handled as CVE-2026-47039. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in Oracle Database Server up to 19.31/21.22/23.26.2. It has been declared as problematic. Affected by this vulnerability is some unknown processing of the component Java VM. The manipulation with an unknown input leads to a improper authorization vulnerability. The CWE definition for the vulnerability is CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect integrity. The summary by CVE is:

Vulnerability in the Java VM 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 low privileged attacker having Create Session privilege with network access via Oracle Net to compromise Java VM. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Java VM accessible data. CVSS 3.1 Base Score 6.5 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N).

The advisory is shared at oracle.com. This vulnerability is known as CVE-2026-47039 since 05/18/2026. The exploitation appears to be easy. The attack can be launched remotely. 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). MITRE ATT&CK project uses the attack technique T1548.002 for this issue.

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