CVE-2026-28667

Analyzed Analyzed - Analysis Complete

Out-of-Bounds Read in Android rw_t5t.cc

Publication date: 2026-10-05

Last updated on: 2026-10-07

Assigner: Android (associated with Google Inc. or Open Handset Alliance)

Description

In multiple functions of rw_t5t.cc, there is a possible out-of-bounds read due to a missing bounds check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-10-05

Last Modified

2026-10-07

Generated

2026-10-19

AI Q&A

2026-10-05

EPSS Evaluated

2026-10-18

NVD

CVE-2026-28667

EUVD

EUVD-2026-92598

Affected Vendors & Products

Vendor	Product	Version / Range
google	android	14.0
google	android	15.0
google	android	16.0
google	android	16.0
google	android	17.0

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-119	The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.

Attack-Flow Graph

Executive Summary

This vulnerability is an out-of-bounds read issue in the rw_t5t.cc file. It occurs because certain functions lack proper bounds checking, allowing a program to read memory outside the intended range. This can lead to local information disclosure without requiring additional privileges or user interaction.

Detection Guidance

This vulnerability is specific to Android's NFC stack (rw_t5t.cc) and requires code-level detection. No direct network or system commands can detect it as it involves a missing bounds check in a library function. Review the Android NFC stack source code for functions in rw_t5t.cc to identify the missing bounds check.

Impact Analysis

An attacker could exploit this to access sensitive data stored in memory on your device. Since no extra permissions or user action are needed, it poses a risk to confidentiality. However, the impact depends on what data is stored in the affected memory regions.

Compliance Impact

This vulnerability could lead to local information disclosure, which may result in unauthorized access to sensitive data. For GDPR, this could impact compliance by exposing personal data without proper authorization. For HIPAA, it may risk unauthorized disclosure of protected health information.

Mitigation Strategies

Apply the latest security patches from Google for Android to address the out-of-bounds read issue in rw_t5t.cc. Ensure all affected devices are updated to the latest firmware version.

Hi! I’m here to help you understand CVE-2026-28667. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70