CVE-2011-1286 json
Google V8, as used in Google Chrome before 10.0.648.127, allows remote attackers to cause a denial of service or possibly have unspecified…
published 2011-03-11 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-1294
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 75%
- public exploits
- 0
- none known
Summary
Google V8, as used in Google Chrome before 10.0.648.127, allows remote attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors that trigger incorrect access to memory.
Patch / fix
- google chrome 10.0.648.127
Exploit prediction
1.60% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Technology feeds
References
-
code.google.com
/p/chromium/issues/detail?id=74675
issue-tracking, vendor-advisory
-
googlechromereleases.blogspot.com
/2011/03/chrome-stable-release.html
vendor-advisory
-
securityfocus.com
/bid/46785
vdb-entry, third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/65970
vdb-entry, third-party-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14455
vdb-entry, signature, third-party-advisory
-
vupen.com
/english/advisories/2011/0628
vdb-entry, permissions-required
Sources
- CVE List CVE-2011-1286
- NVD CVE-2011-1286
Fencer Intel 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.