In NFC, there is a possible out of bounds write due to uninitialized data.

published 2020-09-18 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-1829

cvss: 6.7; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.1%; EPSS 0.1% chance of exploitation in 30 days, percentile 4%
public exploits: 0; none known

In NFC, there is a possible out of bounds write due to uninitialized data. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11Android ID: A-146453119

Exploit prediction

0.15% chance of exploitation in the next 30 days, higher than 4% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
NVD	3.1	6.7	CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	4.6	AV:L/AC:L/Au:N/C:P/I:P/A:P

Affected products

n/a Android

Classification

Weakness

CWE-787 Out-of-bounds Write
CWE-908 Use of Uninitialized Resource

References

source.android.com /security/bulletin/android-11
vendor-advisory

Sources

CVE List CVE-2020-0326
NVD CVE-2020-0326

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary