⚠ Known Exploited Vulnerability (KEV) Tracker

Description

Google Pixel devices contain an improper authorization vulnerability in the cellular modem. A logic error may allow an attacker to bypass permission checks and escalate privileges.

Lifecycle Timeline

• 2026-09-15
  CVE published

  Entered the public CVE record.

  CVE.org →
• 2026-09-16
  Added to CISA KEV 1 day later

  Listed as known exploited, which starts the federal remediation clock.

  CISA KEV →
• 2026-09-19
  Federal remediation due 3 days later

  Deadline for federal civilian agencies under BOD 22-01 — now passed.

  CISA KEV
• not recorded
  Public exploit code

  No dated exploit found in Metasploit, Exploit-DB or public GitHub repositories.
• not recorded
  EPSS flags exploitation risk

  Tracked, and has never reached 10% (peak 0.2%).
• not recorded
  First national advisory

  No tracked government advisory analyses this CVE. Routine KEV catalog-addition alerts do not count here.
• not recorded
  Vendor fix published

  No dated vendor fix. Only Microsoft publishes a machine-readable release date; other vendors state a fixed version without one.

Each milestone comes from a different source, so gaps between them are gaps in what those sources publish, not evidence that nothing happened. EPSS history for this CVE holds 7 points from 2026-09-16, tracked daily from 2026-09-16; earlier points are weekly, which dates a spike to within a week. Peak probability 0.2% on 2026-09-17.

Published Applicability

Check whether a specific version is affected →

What each source publishes about which product versions carry this vulnerability, kept as written rather than merged. Absence here means no source has published applicability data, not that nothing is affected.

Research & News Coverage

Articles from monitored vendor research blogs and security news feeds that specifically mention this CVE. Coverage begins when feed monitoring started; earlier articles are not indexed.

Detection & Exploitation

Blind spot. No public detection — verify by version/patch. Nothing in the monitored scanner, IDS, SIEM or offensive-tool collections references this CVE, so exposure has to be established from asset inventory and patch level rather than from a signature.

Coverage across public collections only: Nuclei and OpenVAS NVT (scan); Snort and Suricata ET Open (network); Sigma and YARA (host/SIEM); Metasploit, Exploit-DB and public GitHub repositories (exploit). Absence here means nothing public was found, not that detection is impossible.
GitHub PoC repositories are collected automatically by PoC-in-GitHub (CC0) and are not vetted: some are fakes and some are malware. Treat them as evidence that code was published, not as code to run.
OpenVAS coverage derives from the Greenbone Community Feed, made available under the Open Database License (ODbL) v1.0; its individual Vulnerability Tests are licensed GNU GPL v2.

CISA Assessment (Vulnrichment / SSVC)

D3FEND Countermeasures

Defensive techniques inferred by MITRE D3FEND from the underlying weakness (CWE-693) — general hardening and detection guidance for this weakness class, not a vendor patch for this specific CVE.

KEV Catalog Status

Listed By

Referenced in Advisories

Weaponization Timeline — Offensive & Testing Tools

No exploit-tool sightings recorded for this CVE.

Evidence tiers are explained on the About page — a merged Metasploit module is far stronger evidence than a distro package mention.

External References

CVE.org record → NVD entry → CISA KEV catalog → FortiGuard Labs → Rapid7 AttackerKB →