{"id":"CVE-2019-1044","url":"https://www.cyber-defence.io/tools/cve/CVE-2019-1044","generatedAt":"2026-10-29T01:54:39.354Z","title":"A security feature bypass vulnerability exists when Windows Secure Kernel Mode fails to properly handle objects in memory.","description":"A security feature bypass vulnerability exists when Windows Secure Kernel Mode fails to properly handle objects in memory.\nTo exploit the vulnerability, a locally-authenticated attacker could attempt to run a specially crafted application on a targeted system. An attacker who successfully exploited the vulnerability could violate virtual trust levels (VTL).\nThe update addresses the vulnerability by correcting how Windows Secure Kernel Mode handles objects in memory to properly enforce VTLs.","published":"2019-06-12T14:29:04.000Z","lastModified":"2026-06-17T02:27:41.000Z","status":"Modified","sourceIdentifier":"secure@microsoft.com","cvss":{"version":"3.1","score":5.3,"severity":"MEDIUM","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L"},"cwe":[],"affected":["microsoft/windows 10","microsoft/windows server 2019"],"epss":{"score":0.01014,"percentile":0.63084,"date":"2026-10-27","history":[]},"kev":{"listed":false},"exploits":{"count":0,"verified":false,"firstPublished":null,"source":"Exploit-DB (https://gitlab.com/exploit-database/exploitdb)","entries":[]},"verdict":{"level":"low","text":"Lower severity and a low EPSS score (1.01%). Track it; it rarely justifies an emergency change on its own."},"changes":[],"references":[{"url":"https://msrc.microsoft.com/update-guide/vulnerability/CVE-2019-1044","source":"secure@microsoft.com"},{"url":"https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1044","tags":["Patch","Vendor Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"}],"sources":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2019-1044","epss":"https://www.first.org/epss/","kev":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","exploitdb":"https://www.exploit-db.com/"},"licence":"CC BY 4.0 — link back to the CVE Explorer if you publish the results; upstream data remains subject to its own terms."}