CVE-2026-0083

Analyzed Analyzed - Analysis Complete

BaseFortify

Publication date: 2026-06-17

Last updated on: 2026-06-18

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

Description

In Nfc::eventCallback() of Nfc.h, there is a possible use after free due to a race condition. 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-17

Last Modified

2026-06-18

Generated

2026-10-16

AI Q&A

2026-06-17

EPSS Evaluated

2026-10-14

NVD

CVE-2026-0083

EUVD

EUVD-2026-37571

Affected Vendors & Products

Vendor	Product	Version / Range
google	android	17.0

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-362	The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

Attack-Flow Graph

Executive Summary

This vulnerability occurs in the Nfc::eventCallback() function of Nfc.h, where a race condition can cause a use after free error. This means that the program might try to use memory after it has been freed, leading to unpredictable behavior.

Exploitation of this flaw can result in a local escalation of privilege without requiring any additional execution privileges or user interaction.

Impact Analysis

The impact of this vulnerability is a local escalation of privilege, meaning an attacker who already has some access to the system could gain higher privileges.

Since no user interaction or additional execution privileges are needed, an attacker could exploit this vulnerability to gain unauthorized control or access to sensitive parts of the system.

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

0/70