Pixel vulnerabilitiesAnd the versions its exploited flaws hit.

Product1 known exploited0 versions
The short answer

Pixel is made by Google. We track 7 published vulnerabilities listed under that exact name, across 0 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 4 April 2024. Google lists newer releases under their own names, such as Pixel C, so check those pages too.

Check your version

The most recent Pixel flaw added to the known-exploited list is CVE-2024-29748, on 4 April 2024. We keep watching the known-exploited list.

Versions

Which versions of Pixel do the exploited flaws hit?

Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.

Known exploited

Which Pixel vulnerabilities are being exploited?

1 flaw is on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.

  1. 7.8
    CVE-2024-29748HighKnown exploited
    Android Pixel Privilege Escalation Vulnerability

    Android Pixel contains a privilege escalation vulnerability that allows an attacker to interrupt a factory reset triggered by a device admin app.

    Chance of use0.7%Known exploited since4 Apr 2024
Exploit likelihood

Which Pixel 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. 9.8%

    The Infineon RSA library 1.02.013 in Infineon Trusted Platform Module (TPM) firmware, such as versions before 0000000000000422 - 4.34, before 000000000000062b - 6.43, and before 0000000000008521 - 133.33, mishandles...

    CVSS5.9Published16 Oct 2017
  2. 0.7%
    CVE-2024-29748HighKnown exploited

    there is a possible way to bypass due to a logic error in the code.

    CVSS7.8Published5 Apr 2024
  3. 0.3%

    An Information Disclosure vulnerability exists in the Google Pixel/Pixel SL Qualcomm Avtimer Driver due to a NULL pointer dereference when processing an accept system call by the user process on AF_MSM_IPC sockets,...

    CVSS5.5Published8 Jan 2020
  4. 0.2%

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

    CVSS7.5Published25 Oct 2024
  5. 0.2%

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

    CVSS7.5Published25 Oct 2024
  6. 0.2%

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

    CVSS7.5Published25 Oct 2024
  7. <0.1%

    There is a possible information disclosure due to a missing permission check.

    CVSS5.5Published2 Jan 2024
EdgeProtect

Running Pixel? 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, across 0 versions. The most recent Pixel flaw added to the known-exploited list is CVE-2024-29748, on 4 April 2024.

1 is on the list of flaws known to be exploited. The most recently added is CVE-2024-29748.

Google also lists Pixel under more specific names, such as Pixel C and Pixel 6. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.

Create a EdgeProtect account and track Pixel. 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.