CVE-2026-55269

Published Oct 5, 2026 CVSS 3.1 · 7.8 High EPSS < 1% KEV · Not listed
Description
In FilterCapturedPacket of snoop_logger.cc, there is a possible memory safety issue due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Analysis

AI-generated

Technical impact

The vulnerability exists in the FilterCapturedPacket function of snoop_logger.cc, where improper input validation (CWE-20) can trigger a memory safety issue. This flaw allows local attackers to gain elevated privileges on an Android device without needing execution rights beyond those already possessed by the user. No user interaction is required for exploitation, meaning a malicious actor can trigger the issue with minimal effort.

Affected Systems

Android devices powered by Google may be impacted. The affected versions are not specified in the advisory, so any device running Android OS that includes the snoop_logger component could be vulnerable until a patch is applied.

Risk and Exploitability

The CVSS score of 7.8 indicates high severity, and the EPSS score is not available while the vulnerability is not listed in CISA KEV, indicating no publicly confirmed exploitation yet. However, because the flaw leads to local privilege escalation and does not rely on external user interaction, the risk is significant for any device that has not applied a fix. Attackers with local access can exploit the memory safety issue directly through the snoop_logger API to elevate privileges, potentially compromising additional system resources. The lack of an elevated execution prerequisite means standard user‑level attacks can succeed immediately.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Install the latest Android security patch from official vendor channels as soon as it becomes available.
  • Disable or restrict access to the snoop_logger component via device management policies or system settings to reduce the attack surface for local privilege escalation.
  • Enforce least‑privilege access controls to ensure that only trusted system processes can invoke the snoop_logger API, preventing untrusted users from triggering the vulnerability.

Generated by OpenCVE AI on October 5, 2026 at 22:42 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:o:google:android:16.0:-:*:*:*:*:*:*
cpe:2.3:o:google:android:16.0:qpr2:*:*:*:*:*:*
cpe:2.3:o:google:android:17.0:-:*:*:*:*:*:*
Type Values Removed Values Added
Title Local Privilege Escal via Improper Input Validation in Android Snoop Logger
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Title Local Privilege Escal via Improper Input Validation in Android Snoop Logger
First Time appeared Google
Google android
Weaknesses CWE-20
Vendors & Products Google
Google android
Type Values Removed Values Added
Description In FilterCapturedPacket of snoop_logger.cc, there is a possible memory safety issue due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
References
Weaknesses
  • CWE-20

    Improper Input Validation

Sources

Status
PUBLISHED
Assigner
google_android
Published
Updated
Oct 6, 2026, 3:56 AM
Reserved
Jun 16, 2026, 5:39 PM
Status
Analyzed
Published
Oct 5, 2026, 7:17 PM
Modified
Oct 7, 2026, 3:10 PM