CVE-2019-3026 json
Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core).
published 2019-10-16 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-12665
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 59%
- public exploits
- 0
- none known
Summary
Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are Prior to 5.2.34 and prior to 6.0.14. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle VM VirtualBox accessible data. CVSS 3.0 Base Score 6.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N).
Patch / fix
- Oracle Corporation VM VirtualBox 5.2.34, 6.0.14
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.89% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N |
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:P/I:N/A:N |
Affected products
- Oracle Corporation VM VirtualBox
References
-
oracle.com
/technetwork/security-advisory/cpuoct2019-5072832.html
patch, vendor-advisory
-
security.gentoo.org
/glsa/202004-02
vendor-advisory, third-party-advisory
-
security.gentoo.org
/glsa/202101-09
vendor-advisory, third-party-advisory
-
zerodayinitiative.com
/advisories/ZDI-19-917/
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2019-3026
- NVD CVE-2019-3026
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.