CVE-2025-53070: Oracle Solaris · Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure
Affects Oracle SolarisSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 26 Oct 2026, 08:30 UTC
- 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:L/PR:H/UI:R/S:C/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Oct 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Oracleoracle/solarispkg:rpm/oracle/solarisOther 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
1. Restrict and monitor high privileged user accounts on Oracle Solaris systems to minimize the risk of misuse. 2. Implement strict user interaction policies and awareness training to reduce the likelihood of successful social engineering or inadvertent actions by users. 3. Employ robust access controls and multi-factor authentication for administrative access to Solaris infrastructure. 4. Monitor system logs and performance metrics for signs of hangs, crashes, or unusual behavior indicative of exploitation attempts. 5. Isolate Solaris systems from less trusted networks and limit local access to authorized personnel only. 6. Develop and test incident response plans specifically for Solaris availability incidents. 7. Engage with Oracle support to obtain patches or workarounds as soon as they become available and apply them promptly. 8. Consider deploying application whitelisting or behavior-based detection tools to identify anomalous filesystem activity. 9. Regularly audit and review privileged account usage and system configurations to ensure compliance with security best practices. 10. Coordinate with supply chain and third-party vendors to assess the impact on integrated products and apply necessary mitigations.
Description
Vulnerability in the Oracle Solaris product of Oracle Systems (component: Filesystem). The supported version that is affected is 11. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle Solaris executes to compromise Oracle Solaris. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Solaris, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle Solaris. CVSS 3.1 Base Score 5.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:N/I:N/A:H).