CVE-2025-26432
NixOS vulnerability analysis and mitigation

Overview

CVE-2025-26432 is a vulnerability in the Android system component classified as improper handling of length parameter inconsistency (CWE-130), which could lead to local denial of service. It affects Android 15.0 and was disclosed as part of the Android Security Bulletin dated June 1, 2025, with NVD publication on September 4, 2025. The vulnerability carries a CVSS v3.1 base score of 5.5 (Medium), requiring only low-privilege local access with no user interaction needed (Android Bulletin).

Technical details

The root cause is classified as CWE-130 (Improper Handling of Length Parameter Inconsistency), located within Android's frameworks/base component. An attacker with low-privilege local access can exploit inconsistent length parameter handling to trigger an availability impact — specifically a denial of service condition — without requiring elevated privileges or user interaction. The patch was committed to the Android Open Source Project (AOSP) at android.googlesource.com/platform/frameworks/base (Android Bulletin, AOSP Patch).

Impact

Successful exploitation results in a denial of service affecting the availability of the targeted Android 15.0 device, with no confidentiality or integrity impact. A local attacker with minimal privileges can disrupt system availability without any user interaction, potentially causing application or system crashes. The scope is limited to the affected device and does not facilitate lateral movement or data exfiltration (Android Bulletin).

Exploitability

There is no public proof-of-concept exploit available, and no evidence of in-the-wild exploitation has been reported. The EPSS score is extremely low at 0.000090, indicating a very low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. No threat actor attribution has been identified (Android Bulletin).

Mitigation and workarounds

Google addressed this vulnerability in the Android Security Bulletin for June 1, 2025. Users and administrators should apply the June 2025 Android security patch level (2025-06-01) or later to affected Android 15.0 devices. OEM patches incorporating this fix have been distributed by Samsung (One UI June 2025 patch) and Xiaomi (HyperOS June 2025 security patch). No configuration-based workaround is publicly documented; patching is the recommended remediation (Android Bulletin, Samsung Details).

Community reactions

The vulnerability received routine coverage as part of the broader Android June 2025 Patch Day. Heise reported on the patch day noting that Android vulnerabilities in this bulletin could allow attackers to gain higher privileges. Samsung and Xiaomi both published details about their respective OEM patches incorporating the June 2025 Android security fixes (Heise Report, Samsung Details).

Additional resources


SourceThis report was generated using AI

Related NixOS vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-78662HIGH7.5
  • Docker logoDocker
  • telegraf-1.38
NoYesSep 02, 2026
CVE-2026-56855HIGH7.5
  • Docker logoDocker
  • flux-notification-controller
NoYesSep 02, 2026
CVE-2026-84642HIGH7.5
  • NixOS logoNixOS
  • cpe:2.3:a:mozilla:thunderbird
NoYesSep 01, 2026
CVE-2026-84641HIGH7.5
  • NixOS logoNixOS
  • thunderbird
NoYesSep 01, 2026
CVE-2026-84640HIGH7.5
  • NixOS logoNixOS
  • cpe:2.3:a:mozilla:thunderbird
NoYesSep 01, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management