Pixel C vulnerabilitiesRanked by how likely they are to be used.

Product0 versions
The short answer

Pixel C is made by Google. We track 7 published vulnerabilities in it, across 0 versions. None of them is on the list of flaws known to be exploited today. If you run Pixel C, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Pixel C vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Pixel C's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Pixel C 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.

50% or more10% to 49%Under 10%
  1. 0.4%

    Buffer overflow in nvhost_job.c in the NVIDIA video driver for Android, Shield TV before OTA 3.3, Shield Table before OTA 4.4, and Shield Table TK1 before OTA 1.5.

    CVSS7.8Published24 Apr 2017
  2. 0.4%

    Stack-based buffer overflow in nvhost_job.c in the NVIDIA video driver for Android, Shield TV before OTA 3.3, Shield Table before OTA 4.4, and Shield Table TK1 before OTA 1.5.

    CVSS7.8Published24 Apr 2017
  3. 0.4%

    Integer overflow in nvhost_job.c in the NVIDIA video driver for Android, Shield TV before OTA 3.3, Shield Table before OTA 4.4, and Shield Table TK1 before OTA 1.5 allows local users to cause a denial of service...

    CVSS7.8Published24 Apr 2017
  4. 0.4%

    mediaserver in Android 4.x before 4.4.4, 5.0.x before 5.0.2, 5.1.x before 5.1.1, and 6.x before 2016-05-01 does not initialize certain data structures, which allows attackers to obtain sensitive information via a...

    CVSS5.5Published9 May 2016
  5. 0.3%

    Android before 2024-10-05 on Google Pixel devices allows information disclosure in the modem component, A-299774545.

    CVSS7.5Published25 Oct 2024
  6. 0.2%

    Android before 2024-10-05 on Google Pixel devices allows information disclosure in the ABL component, A-331966488.

    CVSS7.5Published25 Oct 2024
  7. 0.2%

    Android before 2024-10-05 on Google Pixel devices allows information disclosure in the ACPM component, A-331255656.

    CVSS7.5Published25 Oct 2024
Precursor Intelligence

Running Pixel C? 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.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. 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.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 7 published vulnerabilities listed under the name Pixel C, across 0 versions.

None of Pixel C's vulnerabilities is on the list of flaws known to be exploited today.

Create a Precursor Intelligence account and track Pixel C. 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.