Blink vulnerabilitiesRanked by how likely they are to be used.
Blink is made by Google. We track 12 published vulnerabilities in it, across 3 versions. None of them is on the list of flaws known to be exploited today. If you run Blink, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Blink vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Blink's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Blink flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 1.0%CVE-2011-2808Medium
A stale layout root is set as an input element in WebKit in Google Chrome before Blink M13 when a child of a keygen with autofocus is accessed.
- 0.9%CVE-2011-1460Critical
WebKit in Google Chrome before Blink M11 contains a bad cast to RenderBlock when anonymous blocks are renderblocks.
- 0.9%CVE-2011-1298High
An Integer Overflow exists in WebKit in Google Chrome before Blink M11 in the macOS WebCore::GraphicsContext::fillRect function.
- 0.8%CVE-2011-2337Critical
A wrong type is used for a return value from strlen in WebKit in Google Chrome before Blink M12 on 64-bit platforms.
- 0.7%CVE-2011-2353Medium
Use after free vulnerability in documentloader in WebKit in Google Chrome before Blink M13 in DocumentWriter::replaceDocument function.
- 0.7%CVE-2011-1459Medium
The WebKit::WebPluginContainerImpl::handleEvent function in Google Chrome before Blink M11 allows an attacker to cause a denial of service (crash) via the htmlpluginelement.cpp plugin.
- 0.6%CVE-2011-1802Medium
WebKit in Google Chrome before Blink M11 and M12 does not properly handle counter nodes, which allows remote attackers to cause a denial of service (memory corruption).
- 0.6%CVE-2011-2336Medium
An issue exists in WebKit in Google Chrome before Blink M12.
- 0.6%CVE-2011-2335High
A double-free vulnerability exists in WebKit in Google Chrome before Blink M12 in the WebCore::CSSSelector function.
- 0.5%CVE-2011-2334Medium
Use after free vulnerability exists in WebKit in Google Chrome before Blink M12 in RenderLayerwhen removing elements with reflections.
Running Blink? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
A stale layout root is set as an input element in WebKit in Google Chrome before Blink M13 when a child of a keygen with autofocus is accessed.
- Matched to
- Blink on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 12 published vulnerabilities listed under the name Blink, across 3 versions.
None of Blink's vulnerabilities is on the list of flaws known to be exploited today.
Create a EdgeProtect account and track Blink. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.