CriticalCVE-2026-58704

    Android: Protection Mechanism Failure (CVE-2026-58704)

    Published Last modified In CISA KEV since Sources: BSI

    What is affected, what to do

    In Cellular Modem, there is a possible permission bypass due to a logic error in the code. This could lead to remote (proximal/adjacent) escalation of privilege with no additional execution privileges needed.

    The vulnerability is being actively exploited; treat it as a priority. Update Android Pixel to version 2026-09-05, :unknown: to version :2026-09-05. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Google Android eq Android kernel..Android kernel

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    8.8

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    8.8

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: BSI

    0.6 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 49.9

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    162.25 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploitedSource: VulnCheck KEV (opens in a new tab), CIRCL Sightings How we classify
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    8.8 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    8.8
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.6 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    49.9
    High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CISA assessment (SSVC)
    Exploitation: active · not automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 17 September 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-693, CWE-285

    Response and mitigation

    Why act now?

    Prioritisation rationale

    The flaw sits in the modem firmware and can be exploited without authentication or user interaction. The attacker must, however, be within radio range. That rules out mass exploitation but suits targeted operations against selected individuals well. This fits the low model-predicted exploitation likelihood and the absence of known ransomware use. Typical targets are executives, government and critical-infrastructure personnel, and travellers whose phones act as the gateway to MFA, email and internal systems. Organisations with a large Pixel fleet or exposed high-risk individuals should treat this as high priority and enforce patching within days. Where the Pixel footprint is small, the regular patch cycle backed by a compliance block is sufficient.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Deploy the Pixel security update with patch level 2026-09-05 or later. The fix ships in the Pixel-specific September 2026 update. Force the update for all managed Pixel devices through your UEM/MDM (Intune, Workspace ONE, Google Endpoint Management) and prompt users to reboot. Verify on the device under Settings > About phone > Android version > Android security update.
      • Run an inventory: identify every Pixel device in the fleet (corporate and BYOD with a work profile) whose patch level is older than 2026-09-05. Flag out-of-support models that will not receive the September 2026 update as unremediable and start replacement.
      • Tighten compliance: set "Minimum security patch level" to 2026-09-05 in the Android Enterprise compliance policy. Use Conditional Access to block non-compliant devices from M365, VPN and internal apps.
      • Patch high-risk users first: prioritise executives, admins holding privileged credentials on their phone, travellers to high-risk regions and staff at critical-infrastructure sites. Where patching is not immediately possible, swap the handset for a patched loaner.
      • Disable 2G: turn off Settings > Network & internet > SIMs > Allow 2G on all Pixel devices, via policy or user instruction. This reduces exposure to rogue base stations that force downgrades.

    2. Runbook step 2

      Mitigation layers

      • Radio / proximity: the attack vector is the adjacent radio network, realistically a rogue base station (IMSI catcher) or malicious cell within physical range. In sensitive settings (board meetings, trade fairs, foreign travel), keep unpatched devices in airplane mode, which powers down the modem. Use Wi-Fi only, with always-on VPN.
      • Device hardening: on Android 16, enable Advanced Protection where available; among other things, it enforces 2G protection. Also enable the mobile network security notifications (Security & privacy > More security & privacy > Mobile network security), which alert on unencrypted connections and device identifier requests.
      • IAM / least privilege: keep authenticator apps for Tier 0/1 accounts off unpatched devices. Move admin MFA to FIDO2 hardware keys or dedicated, patched handsets. Shorten mobile session token lifetime via Conditional Access sign-in frequency.
      • Data containment: keep corporate data strictly inside the Android Enterprise work profile and enforce app protection policies (copy/paste restriction, encryption). This limits what a compromised device can expose.
      • Network-side control: connect mobile devices only through a separate Wi-Fi segment or ZTNA, never directly to production or OT networks. Restrict device-to-server access to the services actually required.

    3. Runbook step 3

      Detection rules

      • UEM compliance report: export all Android devices with securityPatchLevel < 2026-09-05 daily. In Intune exports or via Graph API (managedDevices, field androidSecurityPatchLevel), filter on manufacturer "Google" and push open cases into ticketing.
      • Mobile Threat Defense: triage alerts from Defender for Endpoint (Android), Lookout or Zimperium covering network anomalies, rogue cell detection, privilege escalation or device integrity. During forensics, also review unexpected modem or RIL crashes in bugreports (logcat radio buffer).
      • Radio monitoring at sensitive sites: deploy rogue base station detection, such as EFF Rayhunter or commercial RF monitoring, at headquarters and critical-infrastructure sites. Correlate alerts on forced 2G downgrade, null cipher or IMSI requests with when high-risk users are on site.
      • User reports: treat Android warnings about "unencrypted connection" or "device identifier requested" as reportable security events. Establish a reporting path to the SOC and match reports to the device record in MDM.
      • Identity telemetry: hunt for anomalous sign-ins from Android devices, such as new device IDs, impossible travel or token replay. KQL starting point: SigninLogs | where DeviceDetail.operatingSystem has "Android" and RiskLevelDuringSignIn in ("medium","high")

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    In Cellular Modem, there is a possible permission bypass due to a logic error in the code. This could lead to remote (proximal/adjacent) escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Source: BSI WID Portal

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    GoogleAndroid
    • Android kernel
    • —
    GoogleAndroid Pixel
    • < 2026-09-05
    • 2026-09-05
    android:unknown:
    • :0
    • Device specific
    • Kernel
    • Pixel-family specific
    • Pixel-family specific:0
    • :2026-09-05
    • —
    • —
    • —
    • Pixel-family specific:2026-09-05

    Vendors and products

    Affected operating systems

    Affected operating systems
    Mobilegoogleandroid—

    Weakness classes (CWE)

    • CWE-693Protection Mechanism Failure

      Pillar

      The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.

      Entry at MITRE CWE-693

    • CWE-285Improper Authorization

      Class

      The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.

      Entry at MITRE CWE-285

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited

    References & sources

    • source.android.comsecurity/bulletin/2026-09-01advisory
    • source.android.comdocs/security/bulletin/pixel/2026/2026-09-01
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2026-58704government-resource
    • pwn.watchpwn.watch: Google Pixel: Google Pixel Improper Authorization Vulnerabilitypwn-watch
    • NVD (NIST)NVD: CVE-2026-58704pwn-watch
    • cisa.govCISA Known Exploited Vulnerabilities Catalogpwn-watch

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: active, automatable: no

      Show 2 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentremoved
      {"id":"CVE-2026-58704","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-09-15T00:00:00+00:00"}
      —
      SSVC assessmentadded
      —
      {"id":"CVE-2026-58704","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-09-17T03:55:54.211554Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    2. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: active, automatable: no

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentchanged
      {"id":"CVE-2026-58704","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-09-16T14:40:04.611590Z"}
      {"id":"CVE-2026-58704","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-09-15T00:00:00+00:00"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    3. Initial analysis by NVDNVD

      Newly listed as affected:
      Show 3 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Product configurationadded
      —
      OR *cpe:2.3:o:google:android:-:*:*:*:*:*:*:*
      Reference typeadded
      —
      Google Devices: https://source.android.com/docs/security/bulletin/pixel/2026/2026-09-01 Types: Vendor Advisory
      Reference typeadded
      —
      CISA-ADP: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-58704 Types: US Government Resource

      Source identifier: nvd@nist.gov

    4. Record modifiedCISA ADP

      CVSS V3.1: AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

      CVSS V3.1: before AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, after —

      Show 2 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      CVSSadded
      —
      AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
      CVSSremoved
      AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
      —

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    5. CISA KEV entry updated9119a7d8…

      4 individual changes: Date Added, Due Date, Required Action, Vulnerability Name

      Show 4 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Date Addedadded
      —
      2026-09-16
      Due Dateadded
      —
      2026-09-16
      Required Actionadded
      —
      2026-09-16
      Vulnerability Nameadded
      —
      2026-09-16

      Source identifier: 9119a7d8-5eab-497f-8521-727c672e3725

    Show 4 older changes

    1. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: active, automatable: no

      Show 2 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Referenceadded
      —
      https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-58704
      SSVC assessmentchanged
      {"id":"CVE-2026-58704","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-09-15T00:00:00+00:00"}
      {"id":"CVE-2026-58704","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-09-16T14:40:04.611590Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    2. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: none known, automatable: no

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentchanged
      {"id":"CVE-2026-58704","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-09-15T18:53:59.828506Z"}
      {"id":"CVE-2026-58704","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-09-15T00:00:00+00:00"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    3. Receivedgoogle.com

      Description added or changed

      Show 3 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      In Cellular Modem, there is a possible permission bypass due to a logic error in the code. This could lead to remote (proximal/adjacent) escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/58xxx/CVE-2026-58704.json">CVE-2026-58704</a>
      Referenceadded
      —
      https://source.android.com/docs/security/bulletin/pixel/2026/2026-09-01

      Source identifier: dsap-vuln-management@google.com

    4. Record modifiedCISA ADP

      CVSS V3.1: AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

      CISA assessment (SSVC): exploitation: none known, automatable: no

      Weakness type: CWE-285, CWE-693

      Show 4 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      CVSSadded
      —
      AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
      Weakness type (CWE)added
      —
      CWE-285
      Weakness type (CWE)added
      —
      CWE-693
      SSVC assessmentadded
      —
      {"id":"CVE-2026-58704","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-09-15T18:53:59.828506Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    Linked CVEs

    Linked CVEs
    MediumCVE-2026-58773Google Android: Out-of-Bounds Write6.7—
    MediumCVE-2026-58767Google Android: security vulnerability6.7—
    HighCVE-2026-58766Google Android: security vulnerability7.8—
    MediumCVE-2026-58765Google Android: security vulnerability6.7—
    MediumCVE-2026-58755Google Android: security vulnerability6.7—
    MediumCVE-2026-58751Google Android: Use-After-Free6.7—
    MediumCVE-2026-58747Google Android: security vulnerability6.7—
    HighCVE-2026-58744Google Android: Improper Input Validation7.8—
    MediumCVE-2026-58739Google Android: security vulnerability6.7—
    HighCVE-2026-58734Google Android: Out-of-Bounds Write7.0—
    MediumCVE-2026-58731Google Android: Out-of-Bounds Read6.2—
    HighCVE-2026-58728Google Android: Memory Corruption7.0—
    MediumCVE-2026-58726Google Android: security vulnerability6.7—
    HighCVE-2026-58724Google Android: Use-After-Free7.0—
    MediumCVE-2026-58721Google Android: Use of Uninitialized Memory4.4—
    MediumCVE-2026-58718Google Android: Improper Input Validation6.7—
    MediumCVE-2026-58716Google Android: Race Condition6.7—
    HighCVE-2026-58710Google Android: Out-of-Bounds Write8.8—
    CriticalCVE-2026-58704Google Pixel Improper Authorization Vulnerability8.8Actively exploited
    HighCVE-2026-58701Google Android: Out-of-Bounds Write7.0—
    HighCVE-2026-58699Google Android: Out-of-Bounds Read8.4—
    MediumCVE-2026-58698Google Android: security vulnerability6.7—
    HighCVE-2026-58695Google Android: security vulnerability7.8—
    HighCVE-2026-58691Google Android: Improper Input Validation8.4—
    Show 86 more CVEs
    Linked CVEs
    HighCVE-2026-58683Google Android: Out-of-Bounds Write8.8—
    HighCVE-2026-58679Google Android: Heap-Based Buffer Overflow8.4—
    HighCVE-2026-58678Google Android: security vulnerability7.8—
    MediumCVE-2026-57042Google Android: security vulnerability6.7—
    MediumCVE-2026-57035Google Android: Out-of-Bounds Write6.7—
    HighCVE-2026-57014Google Android: Out-of-Bounds Write7.8—
    HighCVE-2026-57012Google Android: security vulnerability8.4—
    HighCVE-2026-57008Google Android: Improper Input Validation7.5—
    MediumCVE-2026-57006Google Android: Information Disclosure4.4—
    HighCVE-2026-56997Google Android: Out-of-Bounds Write8.8—
    MediumCVE-2026-56992Google Android: security vulnerability6.7—
    MediumCVE-2026-56989Google Android: Out-of-Bounds Write6.7—
    MediumCVE-2026-56988Google Android: Use-After-Free6.4—
    HighCVE-2026-56986Google Android: Out-of-Bounds Read8.4—
    HighCVE-2026-56985Google Android: Type Confusion8.4—
    HighCVE-2026-56982Google Android: security vulnerability7.8—
    MediumCVE-2026-56979Google Android: security vulnerability6.7—
    HighCVE-2026-56978Google Android: Out-of-Bounds Read8.4—
    MediumCVE-2026-56975Google Android: Improper Input Validation6.5—
    HighCVE-2026-56974Google Android: Out-of-Bounds Write8.8—
    MediumCVE-2026-56973Google Android: security vulnerability6.7—
    MediumCVE-2026-56972Google Android: Out-of-Bounds Write6.7—
    HighCVE-2026-56970Google Android: security vulnerability8.4—
    HighCVE-2026-56967Google Android: Heap-Based Buffer Overflow8.0—
    MediumCVE-2026-56964Google Android: Use-After-Free6.4—
    CriticalCVE-2026-56960Google Android: Use-After-Free9.8—
    MediumCVE-2026-56958Google Android: Out-of-Bounds Read5.5—
    MediumCVE-2026-56950Google Android: Improper Input Validation4.4—
    HighCVE-2026-56945Google Android: Out-of-Bounds Write7.8—
    HighCVE-2026-56942Google Android: Out-of-Bounds Write8.8—
    HighCVE-2026-56941Google Android: Use-After-Free8.4—
    MediumCVE-2026-56932Google Android: Memory Corruption6.7—
    MediumCVE-2026-56923Google Android: Memory Corruption6.4—
    MediumCVE-2026-56922Google Android: security vulnerability6.7—
    HighCVE-2026-56920Google Android: Out-of-Bounds Write8.8—
    MediumCVE-2026-56915Google Android: Race Condition6.4—
    HighCVE-2026-56914Google Android: Use-After-Free8.4—
    MediumCVE-2026-56907Google Android: Improper Input Validation6.7—
    Not ratedCVE-2026-56900Google Android Pixel: security vulnerability——
    Not ratedCVE-2026-56896Google Android Pixel: security vulnerability——
    MediumCVE-2026-56892Google Android: Information Disclosure6.2—
    Not ratedCVE-2026-56891Google Android Pixel: security vulnerability——
    MediumCVE-2026-56889Google Android: Integer Overflow6.7—
    MediumCVE-2026-56888Google Android: Information Disclosure6.2—
    Not ratedCVE-2026-56886Google Android Pixel: security vulnerability——
    Not ratedCVE-2026-56885Google Android Pixel: security vulnerability——
    HighCVE-2026-56882Google Android: Information Disclosure8.8—
    HighCVE-2026-56881Google Android: security vulnerability8.4—
    MediumCVE-2026-56879Google Android: Memory Corruption6.7—
    CriticalCVE-2026-55366Google Android: Authentication Bypass9.8—
    MediumCVE-2026-55365Google Android: Out-of-Bounds Write6.7—
    Not ratedCVE-2026-55364Google Android Pixel: security vulnerability——
    HighCVE-2026-55359Google Android: security vulnerability7.8—
    Not ratedCVE-2026-55358Google Android Pixel: security vulnerability——
    Not ratedCVE-2026-55357Google Android Pixel: security vulnerability——
    Not ratedCVE-2026-55355Google Android Pixel: security vulnerability——
    HighCVE-2026-55351Google Android: Out-of-Bounds Write7.8—
    HighCVE-2026-55343Google Android: Out-of-Bounds Write8.0—
    Not ratedCVE-2026-55337Google Android Pixel: security vulnerability——
    MediumCVE-2026-55332Google Android: Out-of-Bounds Write6.7—
    HighCVE-2026-55331Google Android: Out-of-Bounds Write8.8—
    Not ratedCVE-2026-55329Google Android Pixel: security vulnerability——
    Not ratedCVE-2026-55326Google Android Pixel: security vulnerability——
    HighCVE-2026-55323Google Android: Heap-Based Buffer Overflow7.8—
    HighCVE-2026-55318Google Android: Use-After-Free8.8—
    MediumCVE-2026-55317Google Android: Out-of-Bounds Write6.7—
    HighCVE-2026-55306Google Android: Improper Input Validation7.5—
    Not ratedCVE-2026-55305Google Android Pixel: security vulnerability——
    MediumCVE-2026-55304Google Android: security vulnerability6.7—
    MediumCVE-2026-55302Google Android: security vulnerability6.7—
    HighCVE-2026-55301Google Android: Out-of-Bounds Write8.4—
    Not ratedCVE-2026-28589Google Android Pixel: security vulnerability——
    HighCVE-2026-0200Google Android: Heap-Based Buffer Overflow8.8—
    HighCVE-2026-0199Google Android: Out-of-Bounds Write7.8—
    MediumCVE-2026-0197Google Android: Information Disclosure4.4—
    HighCVE-2026-0194Google Android: Integer Overflow8.4—
    MediumCVE-2026-0192Google Android: security vulnerability6.7—
    HighCVE-2026-0189Google Android: security vulnerability8.4—
    MediumCVE-2026-0187Google Android: security vulnerability6.7—
    MediumCVE-2026-0186Google Android: security vulnerability6.7—
    MediumCVE-2026-0183Google Android: Information Disclosure4.4—
    MediumCVE-2026-0179Google Android: security vulnerability6.7—
    MediumCVE-2026-0177Google Android: Out-of-Bounds Read4.4—
    HighCVE-2026-0171Google Android: Out-of-Bounds Write8.8—
    HighCVE-2026-0170Google Android: Out-of-Bounds Write8.8—
    HighCVE-2026-0159Google Android: Out-of-Bounds Write8.8—

    Linked advisories

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-58704
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-58704"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-58704.svg?lang=en" alt="CVE-2026-58704 – NEOSEC Intel" height="20"></a>