CVE-2026-21975: Oracle Database Server · Easily exploitable vulnerability allows high privileged attacker having Authenticated User privilege
Affects Oracle Database ServerSource CVE Database V5
Not known to be exploited · CVSS 4.5 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 Jan 2026
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-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Oracle CorporationOracle Database Server | 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-2026-21975, European organizations should: 1) Apply Oracle's security patches or updates as soon as they become available for the affected Oracle Database versions. 2) Restrict network access to Oracle Net services to trusted hosts and networks only, using firewalls and network segmentation to limit exposure. 3) Enforce the principle of least privilege by limiting high privileged user accounts and monitoring their activity closely. 4) Educate users about social engineering risks to reduce the likelihood of successful user interaction required for exploitation. 5) Disable or remove unnecessary Java VM components or features within Oracle Database if not required for business processes. 6) Implement robust monitoring and alerting for unusual database or Java VM crashes to detect potential exploitation attempts early. 7) Regularly review and audit Oracle Database configurations and user privileges to ensure compliance with security best practices. These steps go beyond generic advice by focusing on reducing attack surface, controlling privileged access, and enhancing detection capabilities specific to this vulnerability.
Description
Vulnerability in the Java VM component of Oracle Database Server. Supported versions that are affected are 19.3-19.29 and 21.3-21.20. Easily exploitable vulnerability allows high privileged attacker having Authenticated User privilege with network access via Oracle Net to compromise Java VM. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Java VM. CVSS 3.1 Base Score 4.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:N/A:H).