CVE-2009-2935 in the critical feed json
Google V8, as used in Google Chrome before 2.0.172.43, allows remote attackers to bypass intended restrictions on reading memory, and possi…
published 2009-08-27 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-2923
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 5.7%
- EPSS 5.7% chance of exploitation in 30 days, percentile 93%
- public exploits
- 0
- none known
Summary
Google V8, as used in Google Chrome before 2.0.172.43, allows remote attackers to bypass intended restrictions on reading memory, and possibly obtain sensitive information or execute arbitrary code in the Chrome sandbox, via crafted JavaScript.
Patch / fix
- google chrome 2.0.172.43
Exploit prediction
5.69% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
- Technology feeds
References
-
vupen.com
/english/advisories/2009/2420
vdb-entry, vendor-advisory
-
secunia.com
/advisories/36417
third-party-advisory, vendor-advisory
-
googlechromereleases.blogspot.com
/2009/08/stable-update-security-fixes.html
vendor-advisory
-
code.google.com
/p/chromium/issues/detail?id=18639
vendor-advisory
-
osvdb.org
/57421
vdb-entry
-
securityfocus.com
/bid/36149
vdb-entry
-
securitytracker.com
/id?1022773
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/52902
vdb-entry
Sources
- CVE List CVE-2009-2935
- NVD CVE-2009-2935
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.
CPEs and fixed versions use Anchore's correction of NVD's data: Consolidate version ranges.