Oracle Database Server up to 19.31/21.22/23.26.2 JDBC
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00+ |
Summary
A vulnerability, which was classified as problematic, has been found in Oracle Database Server up to 19.31/21.22/23.26.2. The impacted element is an unknown function of the component JDBC. The manipulation leads to an unknown weakness. This vulnerability is traded as CVE-2026-47060. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability, which was classified as problematic, has been found in Oracle Database Server up to 19.31/21.22/23.26.2. This issue affects an unknown functionality of the component JDBC. Impacted is integrity. 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 unauthenticated attacker 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 unauthorized creation, deletion or modification access to critical data or all JDBC accessible data. CVSS 3.1 Base Score 6.5 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N).
It is possible to read the advisory at oracle.com. The identification of this vulnerability is CVE-2026-47060 since 05/18/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/22/2026).
Upgrading to version 19.31, 21.22 or 23.26.2 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
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
Website
- Vendor: https://www.oracle.com
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: UnknownCWE: Unknown
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Upgrade: Database Server 19.31/21.22/23.26.2
Timeline
05/18/2026 CVE reserved07/21/2026 VulDB entry created
07/22/2026 Advisory disclosed
07/22/2026 VulDB entry last update
Sources
Vendor: oracle.comAdvisory: oracle.com
Status: Confirmed
CVE: CVE-2026-47060 (🔒)
GCVE (CVE): GCVE-0-2026-47060
GCVE (VulDB): GCVE-100-381179
Entry
Created: 07/22/2026 00:52Changes: 07/22/2026 00:52 (53)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.