VulnSocial

CVE-2026-28580Disclosure(google / android)

LOWCVSS 7.8 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

In multiple functions, there is a possible desync in persistence due to an incorrect bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

google CVEsBack to dashboard
0.0/ 10 priority

Sources & remediation

Vendor / third-party advisories
Weakness type (CWE)
CWE-120

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

STABLE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • android

Threat summary

  • 3 mentions across 2 observed days
  • Momentum state: stable

What's happening

  • Technical details provided in 3 signals
  • Disclosure: 2 classified signals
  • General: 1 classified signal
  • Peaked 1d ago at 2 mentions (2026-06-01); latest day: 1
  • 3 total mentions across 2 days

Affected systems

Vendors
google
Products
android

1 version affected across 1 product

Deep dive

Activity timeline3 mentions / 2d
01122Mentions · 2026-06-01: 2Mentions · 2026-06-02: 1Technical Details · 2026-06-01: 2Technical Details · 2026-06-02: 106-0106-02
Signal classification2 categories
Disclosure
266.7%
General
133.3%
Referenced assets3 URLs
Classification over time
DateTotalLabels
2026-06-012
Disclosure1General1
2026-06-021
Disclosure1
Full discourse3 posts
  • DailyCVE@dailycve
    Disclosure

    🔴 #Android (#Google), Desynchronization in Persistence, #CVE-2026-28580 (Critical) -DC-Jun2026-150 https://dailycve.com/android-google-desynchronization-in-persistence-cve-2026-28580-critical-dc-jun2026-150/

    Post summary

    A new Android CVE‑2026‑28580 involving a persistence desynchronization flaw has been disclosed as critical, yet the brief post does not provide any PoC, exploit, patch, or active‑exploitation information.

    0000037
    209 followersView on X
  • Infoflowcloud@infoflowcloud
    Disclosure

    🚨*CVE* CVE-2026-28580 In multiple functions, there is a possible desync in persistence due to an incorrect bounds check. This could lead to local escalation of privilege with no additional… https://www.cve.org/CVERecord?id=CVE-2026-28580 ----- Traducción: CVE-2026-28580 En … http://infoflow.cloud`

    Post summary

    The post announces CVE-2026-28580, describing a bounds‑check desynchronization that could lead to local privilege escalation, but it offers no PoC, exploit, active‑use claim, patch, or debunking.

    0000020
    79 followersView on X
  • CVE@CVEnew
    General

    CVE-2026-28580 In multiple functions, there is a possible desync in persistence due to an incorrect bounds check. This could lead to local escalation of privilege with no additional… https://www.cve.org/CVERecord?id=CVE-2026-28580

    Post summary

    The passage only outlines the technical details of CVE-2026-28580, noting a desynchronization issue leading to local privilege escalation, without mentioning any Proof of Concept, exploit tools, active attacks, patches, or false positive claims.

    00000282
    57.6K followersView on X
CPE platform detail4 entries

4 of 4 entries

PartVendorProductVersionTarget SWTarget HW
OSgoogleandroid16.0--
OSgoogleandroid16.0--
OSgoogleandroid16.0--
OSgoogleandroid16.0--

Explore more

Back to dashboardgoogle CVEsandroid vulnerabilities