CVE-2011-1456 json
Google Chrome before 11.0.696.57 does not properly handle PDF forms, which allows remote attackers to cause a denial of service or possibly…
published 2011-05-03 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-1461
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 64%
- public exploits
- 0
- none known
Summary
Google Chrome before 11.0.696.57 does not properly handle PDF forms, which allows remote attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors that lead to "stale pointers."
Patch / fix
- google chrome 11.0.696.57
Exploit prediction
1.04% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
- Technology feeds
References
-
googlechromereleases.blogspot.com
/2011/04/chrome-stable-update.html
vendor-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14356
vdb-entry, signature, third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/67162
vdb-entry, third-party-advisory
-
code.google.com
/p/chromium/issues/detail?id=79364
permissions-required
Sources
- CVE List CVE-2011-1456
- NVD CVE-2011-1456
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.