CVE-2025-30736: Oracle Database Server · Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple
Affects Oracle Database ServerSource CVE Database V5
Not known to be exploited · CVSS 7.4 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 15 Apr 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Mavencom.oracle.database/oracle-database-serverpkg:maven/com.oracle.database/oracle-database-serverOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2025-30736, organizations should: 1) Monitor Oracle’s official security advisories closely and apply patches promptly once they become available, as no patches are currently linked. 2) Restrict network access to Oracle Database Server instances, especially limiting exposure of Java VM accessible protocols to trusted networks only. 3) Employ network segmentation and firewall rules to minimize attack surface and prevent unauthorized external access. 4) Audit and review database user privileges and Java stored procedures to ensure least privilege principles are enforced. 5) Enable detailed logging and monitoring of Java VM activities within Oracle Database to detect anomalous behavior indicative of exploitation attempts. 6) Consider disabling Java VM features if not required for business operations to reduce attack vectors. 7) Conduct penetration testing and vulnerability assessments focusing on Oracle Database Server Java VM components to identify potential exploitation paths. These targeted steps go beyond generic advice by focusing on limiting exposure of the vulnerable component and enhancing detection capabilities.
Description
Vulnerability in the Java VM component of Oracle Database Server. Supported versions that are affected are 19.3-19.26, 21.3-21.17 and 23.4-23.7. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols 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 as well as unauthorized access to critical data or complete access to all Java VM accessible data. CVSS 3.1 Base Score 7.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N).