CVE-2009-2556 in the critical feed json
Google Chrome before 2.0.172.37 allows attackers to leverage renderer access to cause a denial of service (memory corruption and applicatio…
published 2009-07-21 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-2551
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 78%
- public exploits
- 0
- none known
Summary
Google Chrome before 2.0.172.37 allows attackers to leverage renderer access to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via unspecified vectors that trigger excessive memory allocation.
Patch / fix
- google chrome 2.0.172.37
Exploit prediction
1.77% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
- Technology feeds
References
-
googlechromereleases.blogspot.com
/2009/07/stable-beta-update-bug-fixes.html
vendor-advisory
-
secunia.com
/advisories/35844
third-party-advisory, vendor-advisory
-
vupen.com
/english/advisories/2009/1924
vdb-entry, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/51802
vdb-entry
-
securityfocus.com
/bid/35723
vdb-entry
Sources
- CVE List CVE-2009-2556
- NVD CVE-2009-2556
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.