PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-28668 Google CVE debrief

A logic error in the LimitRealloc function of malloc_limit.cpp could lead to a use-after-free vulnerability, allowing for local escalation of privilege without additional execution privileges needed. This vulnerability affects Android versions 14.0, 15.0, 16.0, and 17.0. The CVE record and NVD entry provide details on the vulnerability, including its CVSS score of 7.8. Android system administrators, security teams, and developers should assess exposure and apply necessary patches or updates.

Vendor
Google
Product
Android
CVSS
HIGH 7.8
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-08
Original CVE updated
2026-09-23
Advisory published
2026-09-08
Advisory updated
2026-09-23

Who should care

Android system administrators, security teams, and developers responsible for maintaining and securing Android systems should assess exposure and apply necessary patches or updates to prevent potential exploitation. This includes reviewing compensating controls for exposed systems, monitoring systems for potential exploitation attempts, and tracking exceptions and retesting remediated assets.

Why it matters

CVE-2026-28668 is a high-severity vulnerability in the Android operating system that could allow local escalation of privilege. Android system administrators, security teams, and developers should assess exposure and apply patches or updates to prevent potential exploitation.

  • Local escalation of privilege without additional execution privileges needed
  • Potential for unauthorized access or control of affected systems
  • Need for patching or updating affected Android versions

Technical summary

The vulnerability exists in the LimitRealloc function of malloc_limit.cpp, which can lead to a use-after-free condition. This could allow an attacker to escalate privileges locally without needing additional execution privileges. The vulnerability affects Android versions 14.0, 15.0, 16.0, and 17.0. The Android Security Team has provided patches for affected versions. Android system administrators, security teams, and developers should assess exposure and apply necessary patches or updates to prevent potential exploitation.

Defensive priority

Assess exposure and apply patches for Android versions 14.0, 15.0, 16.0, and 17.0.

Recommended defensive actions

  • Assess exposure for Android versions 14.0, 15.0, 16.0, and 17.0
  • Apply patches or updates provided by the vendor
  • Monitor systems for potential exploitation attempts
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its CVSS score of 7.8 and affected Android versions. The vulnerability exists in the LimitRealloc function of malloc_limit.cpp, which can lead to a use-after-free condition. This could allow an attacker to escalate privileges locally without needing additional execution privileges. The Android Security Team has provided patches for affected versions.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-28668 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-28668

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-28668 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-28668

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.