Pixel

Related CVEsby mentions

• CVE-2026-587048.8—
  Permission Bypass in Google Pixel Cellular Modem Allows Proximal Privilege Escalation
  A logic error in the cellular modem component causes an improper authorization check (CWE-285/CWE-693), allowing a permission bypass. An attacker who already has low privileges and is on an adjacent network (proximal, e.g., a hostile local or cellular-adjacent network) can trigger the flaw without any user interaction, and successful exploitation yields remote escalation of privilege with high impact on confidentiality, integrity, and availability (CVSS 3.1 base score 8.0). The flaw was assigned through Google's device security CNA ([email protected]), consistent with modem firmware shipped in Google Pixel-class devices; specific affected firmware versions were not provided in the source data. No public proof-of-concept is known, the issue is not listed in CISA's KEV catalog, and there is no evidence of exploitation in the wild. Defenders should treat this as a patch-on-next-bulletin item unless devices operate in high-risk adjacent-network environments.
  · Google Cellular Modem (modem firmware on Google Pixel-class devices, per assigning CNA) KEVmass
• CVE-2025-485958.42%
  Integer Overflow Local Privilege Escalation in Android Framework
  CVE-2025-48595 is an integer overflow (CWE-190) in the Android Framework, present in multiple locations, that can be triggered by code already running locally on the device with no additional execution privileges and no user interaction required. A local attacker, such as a malicious or compromised app, who triggers the overflow can achieve code execution with elevated privileges, yielding a local escalation of privilege with high impact on confidentiality, integrity, and availability (CVSS 3.1: 8.4, local attack vector). The flaw affects the Android Framework component of Google's Android operating system, so it applies broadly across the Android device ecosystem; specific affected version ranges were not published in the available data. Google fixed the flaw in its June 2026 Android security update, which patched 124 flaws overall, and CISA added it to the Known Exploited Vulnerabilities catalog on 2026-06-02, with news coverage confirming it is being actively exploited in the wild. No public proof-of-concept is known, but confirmed in-the-wild exploitation makes patching urgent.
  · Google Android KEVmass
• CVE-2026-850468.81%
  Actively Exploited V8 Type Confusion in Google Chrome (CVE-2026-85046)
  Google Chrome versions prior to 152.0.7977.82 contain a type confusion flaw (CWE-843) in the V8 JavaScript engine, which mishandles object types during engine operations (public proof-of-concept writeups indicate it is reachable through array sorting and WebAssembly-related code paths). A remote attacker triggers the flaw simply by getting a user to open a crafted HTML page, with no privileges or authentication required. Successful exploitation lets the attacker execute arbitrary code inside the browser's sandbox, and public reporting shows it being chained with Windows zero-days (the 'BlueMoon' exploit kit) by Chinese espionage groups for broader compromise. Any user of an unpatched Chrome or another build embedding the affected V8 engine is exposed. The vulnerability is a zero-day that was actively exploited in the wild before patching, was added to CISA's KEV on 2026-09-04, and has five public proof-of-concept references.
  · Google Chrome prior to 152.0.7977.82 · Google Chromium V8 V8 engine versions bundled with Chrome prior to 152.0.7977.82 KEV PoC ×5mass
• CVE-2026-874918.8<1%
  Actively Exploited Out-of-Bounds Write in Google Chrome V8
  CVE-2026-87491 is an out-of-bounds write (CWE-787) in the V8 JavaScript engine in Google Chrome, fixed in Chrome 153.0.8010.36, which Google shipped alongside roughly 230 other security fixes. An attacker can trigger the flaw remotely by luring a user (user interaction required) into opening a crafted HTML page that corrupts memory in V8. Successful exploitation allows the attacker to execute arbitrary code inside the Chrome browser sandbox, which constrains but does not eliminate the impact. All Google Chrome users running versions prior to 153.0.8010.36 are affected; because the flaw resides in V8, CISA tracks it as 'Google Chromium V8', and other Chromium-based browsers may inherit the fix in their own updates. The flaw is being actively exploited in the wild — it is the seventh actively exploited Chrome zero-day of 2026 and was added to CISA's KEV catalog on 2026-09-09 — though no public proof-of-concept is known and ransomware use is unknown.
  · Google Chrome (V8 JavaScript engine; tracked by CISA as 'Google Chromium V8') prior to 153.0.8010.36 KEVmass
• CVE-2026-569148.4—
  Use-After-Free in Google Pixel Modem Enables Local Privilege Escalation
  CVE-2026-56914 is a use-after-free condition caused by improper locking in multiple code locations in the modem component of Google Pixel smartphones, per Google's security bulletin coverage. An attacker can trigger the freed-memory race condition without needing any user interaction and without holding additional execution privileges. Successful exploitation yields local escalation of privilege on the affected device. All Pixel devices running firmware that predates Google's fix are potentially affected, with the specific impacted models and build numbers not enumerated in the available data. There is no public proof-of-concept and the flaw is not in CISA's KEV catalog, but Google's patch release is accompanied by reports of signs of limited, targeted exploitation.
  · Google Pixel smartphones (modem component)mass
• CVE-2026-286628.0<1%
  Heap Buffer Overflow in Android Wi-Fi Direct (P2P) Provisioning Discovery Enables Nearby RCE
  CVE-2026-28662 is a heap buffer overflow causing an out-of-bounds write in p2p_process_prov_disc_bootstrap_req in p2p_pd.c, the code that handles Wi-Fi P2P (Wi-Fi Direct) provisioning discovery bootstrap requests in Android's Wi-Fi stack. It is triggered when a nearby attacker sends a crafted bootstrap request over the air while the device's Wi-Fi is enabled; no user interaction or privileges are required. Successful exploitation yields remote (proximal/adjacent) code execution, meaning anyone within Wi-Fi radio range could run code on the device. Android devices running software prior to the September 2026 Android Security Update are affected. Exploitation is not currently observed: there is no public proof-of-concept, it is not in CISA's KEV, and EPSS puts 30-day exploitation probability at about 0.1%.
  · Google / Android (CNA: [email protected]) Android OS Wi-Fi P2P (Wi-Fi Direct) stack, p2p_process_prov_disc_bootstrap_req in p2p_pd.cmass
• CVE-2026-587736.7—
  Out-of-Bounds Write in Google Pixel Modem Link Driver Enables Local Privilege Escalation
  CVE-2026-58773 is an out-of-bounds write (CWE-787) in link_load_gnss_image of link_device.c, the modem link device driver in the Android kernel used on Google Pixel phones, where a missing bounds check allows memory corruption when a GNSS image is loaded. To trigger it, an attacker must already have System-level code execution on the device; no user interaction is required. Successful exploitation corrupts memory outside the intended bounds and can yield local escalation of privilege, effectively moving an attacker from System context to higher (kernel-level) privileges. The flaw affects Google Pixel devices running the affected modem link driver, so exposure is limited to attackers who have already compromised a device or an app with System privileges. No public proof-of-concept exists and the bug is not in CISA KEV, but reporting indicates signs of limited, targeted exploitation, so it should be treated as exploited in the wild.
  · Google Pixel smartphones - Android kernel modem link device driver (link_device.c, link_load_gnss_image; Tensor/Exynos-modem Pimass

Appears with