CVE-2010-3256 json
Google Chrome before 6.0.472.53 does not properly limit the number of stored autocomplete entries, which has unspecified impact and attack…
published 2010-09-07 16 y ago modified 2026-06-16 4 mo ago also EUVD-2010-3255
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
Google Chrome before 6.0.472.53 does not properly limit the number of stored autocomplete entries, which has unspecified impact and attack vectors.
Patch / fix
Exploit prediction
0.62% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:N/A:P |
Classification
- Technology feeds
References
-
code.google.com
/p/chromium/issues/detail?id=51727
issue-tracking, patch, vendor-advisory
-
googlechromereleases.blogspot.com
/2010/09/stable-and-beta-channel-updates.html
vendor-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A12027
vdb-entry, signature, third-party-advisory
Sources
- CVE List CVE-2010-3256
- NVD CVE-2010-3256
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.