CVE-2026-0100

Analyzed Analyzed - Analysis Complete

Heap Buffer Overflow in Android LoadedArsc

Publication date: 2026-06-01

Last updated on: 2026-06-03

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

Description

In Load of LoadedArsc.cpp, there is a possible out of bounds write due to a heap buffer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-06-01

Last Modified

2026-06-03

Generated

2026-07-12

AI Q&A

2026-06-02

EPSS Evaluated

2026-07-11

NVD

CVE-2026-0100

EUVD

EUVD-2026-33810

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	16.0
google	android	16.0

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-122	A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().

Attack-Flow Graph

Executive Summary

This vulnerability occurs in the Load function of the LoadedArsc.cpp file, where a heap buffer overflow can happen due to an out of bounds write.

It means that the program writes data outside the allocated memory buffer, which can corrupt memory and lead to unexpected behavior.

Exploitation of this vulnerability does not require any user interaction.

Impact Analysis

This vulnerability can lead to local escalation of privilege, allowing an attacker to gain higher privileges on the affected system.

No additional execution privileges are needed to exploit this vulnerability, which increases its risk.

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

0/70