CVE-2026-0082

Google Android 17.0

Published

17 June 2026

Modified

18 June 2026

Patch / advisory

View advisory

CVSS Score v4 10.0

Click a component to see what it means

Raw vector

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

EPSS Score 0.0016 6th percentile

Risk Priority 45 floored blend · peak EPSS

Summary

CVE-2026-0082 is a critical-severity Insecure Default Variable Initialization (CWE-453) vulnerability in Google Android. Its CVSS base score is 10.0 (Critical).

Operationally, ranked at the 6th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to CM-2 (Baseline Configuration) and CM-6 (Configuration Settings) — see the control section below for these in your framework.

EU & UK References

🇪🇺 ENISA EUVD: EUVD-2026-37570

Vulnerability Data

In tryStartActivity of NfcDispatcher.java, there is a possible automatic special app access permission assignment due to an insecure default value. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for…

exploitation.

CWE(s): CWE-453

Related Threats

CVEs Like This One

CVE-2025-48543Same product: Google Android

CVE-2025-36891Same product: Google Android

CVE-2023-40088Same product: Google Android

CVE-2023-21184Same product: Google Android

CVE-2024-43077Same product: Google Android

CVE-2024-43088Same product: Google Android

CVE-2023-21401Same product: Google Android

CVE-2025-48653Same product: Google Android

CVE-2024-47021Same product: Google Android

CVE-2024-29745Same product: Google Android

Affected Assets

google

android

17.0

Mitigating Controls

Control response

Prevent

Stop it (NIST 800-53)

—

Detect

Catch it (NIST detect / respond)

—

Harden

Shrink the surface (DISA STIG)

4 hardening rules · 2 OS baselines

Validate

Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

CM-6 Configuration Settings good match

Requires establishing the most restrictive configuration settings, which directly overrides or prevents use of insecure default variable initializations.

CM-2 Baseline Configuration good match

Requires maintaining a documented baseline configuration that can enforce secure initial values instead of insecure defaults.

SA-8 Security and Privacy Engineering Principles partial match

Mandates application of security engineering principles during development that include use of secure defaults and proper variable initialization.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-01 mostly match

prevents

Hardened baselines and configuration management directly replace insecure product defaults with secure values.

PR.PS-06 mostly match

prevents

Secure software development practices explicitly include choosing safe initial values instead of insecure defaults.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match

finds

Security testing can detect insecure defaults but does not prevent them.

A.8.9 Configuration management mostly match

prevents

Configuration management enforces secure default values and prevents insecure initialization.

A.8.25 Secure development life cycle partial match

prevents

Secure development life cycle requires explicit secure initialization of variables.

A.8.27 Secure system architecture and engineering principles partial match

prevents

Secure architecture principles include avoiding insecure defaults in design.