Skip to main content
CVE-2025-50070VulnerabilityPublished Updated

CVE-2025-50070: Oracle JDBC · Improper Access Control

Affects Oracle JDBCSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Mavencom.oracle.database/jdbcpkg:maven/com.oracle.database/jdbcOther threatsAffected
  • =23.4
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should implement strict access controls to limit authenticated OS user privileges and restrict access to systems running vulnerable JDBC versions. Network segmentation and isolation of critical database infrastructure can reduce the attack surface. Monitoring and alerting on unusual user interactions and access patterns involving JDBC components can help detect attempted exploitation. Since exploitation requires human interaction, user awareness training focusing on social engineering risks is recommended. Oracle customers should track Oracle security advisories closely and apply patches or updates promptly once they become available. In the interim, consider applying compensating controls such as enhanced logging, multi-factor authentication for OS access, and minimizing the number of users with OS-level access to JDBC infrastructure. Conduct regular security assessments and penetration testing to identify potential exploitation paths involving JDBC components.

Description

Vulnerability in the JDBC component of Oracle Database Server. Supported versions that are affected are 23.4-23.8. Difficult to exploit vulnerability allows low privileged attacker having Authenticated OS User privilege with logon to the infrastructure where JDBC executes to compromise JDBC. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in JDBC, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all JDBC accessible data. CVSS 3.1 Base Score 5.3 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N).

References

Community reviews

Loading reviews…