{"id":"CVE-2012-2827","url":"https://www.cyber-defence.io/tools/cve/CVE-2012-2827","generatedAt":"2026-10-27T17:57:34.279Z","title":"Use-after-free vulnerability in the UI in Google Chrome before 20.0.1132.43 on Mac OS X allows attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors.","description":"Use-after-free vulnerability in the UI in Google Chrome before 20.0.1132.43 on Mac OS X allows attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors.","published":"2012-06-27T10:18:39.000Z","lastModified":"2026-06-16T23:42:10.000Z","status":"Modified","sourceIdentifier":"chrome-cve-admin@google.com","cvss":{"version":"2.0","score":7.5,"severity":"HIGH","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P"},"cwe":["CWE-399"],"affected":["google/chrome"],"epss":{"score":0.00639,"percentile":0.50332,"date":"2026-10-26","history":[]},"kev":{"listed":false},"exploits":{"count":0,"verified":false,"firstPublished":null,"source":"Exploit-DB (https://gitlab.com/exploit-database/exploitdb)","entries":[]},"verdict":{"level":"high","text":"High impact if exploited, but EPSS currently rates exploitation as unlikely (0.64%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit."},"changes":[],"references":[{"url":"http://code.google.com/p/chromium/issues/detail?id=129826","source":"chrome-cve-admin@google.com"},{"url":"http://googlechromereleases.blogspot.com/2012/06/stable-channel-update_26.html","source":"chrome-cve-admin@google.com"},{"url":"http://code.google.com/p/chromium/issues/detail?id=129826","source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"http://googlechromereleases.blogspot.com/2012/06/stable-channel-update_26.html","source":"af854a3a-2127-422b-91ae-364da2661108"}],"sources":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2012-2827","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."}