CVE-2026-3932
Google Chrome ≤ 146.0.7680.71
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:NSummary
CVE-2026-3932 is a high-severity Improper Access Control (CWE-284) vulnerability in Google Chrome. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Drive-by Compromise (T1189); ranked at the 8th 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 AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-3932 is an insufficient policy enforcement vulnerability in the PDF component of Google Chrome on Android versions prior to 146.0.7680.71. It enables a remote attacker to bypass navigation restrictions through a crafted HTML page. The issue carries a Chromium security severity rating of Medium and a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N), with associated CWEs including NVD-CWE-noinfo and CWE-284 (Improper Access Control).
A remote attacker can exploit this vulnerability without privileges or user interaction by tricking a victim into visiting a malicious site hosting the crafted HTML page. Successful exploitation allows the attacker to bypass navigation restrictions enforced by the PDF viewer, potentially enabling unauthorized redirects or access to restricted content within the browser context, resulting in high integrity impact.
Mitigation is addressed in the Chrome stable channel update, as detailed in the Google Chrome Releases blog post at https://chromereleases.googleblog.com/2026/03/stable-channel-update-for-desktop_10.html, which covers the patch up to version 146.0.7680.71. Additional technical details are available in the Chromium issue tracker at https://issues.chromium.org/issues/478296121. Security practitioners should ensure Android Chrome users update to version 146.0.7680.71 or later.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-11456
Vulnerability Data
Insufficient policy enforcement in PDF in Google Chrome on Android prior to 146.0.7680.71 allowed a remote attacker to bypass navigation restrictions via a crafted HTML page. (Chromium security severity: Medium)
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
CVE enables client-side exploitation via crafted HTML on malicious site visit (drive-by), bypassing PDF navigation controls in browser without further user interaction.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
AC-3 requires systems to enforce approved access control policies, directly addressing the insufficient policy enforcement in Chrome's PDF viewer that allowed bypassing navigation restrictions via crafted HTML.
AC-4 enforces information flow control policies, preventing unauthorized redirects or access to restricted content resulting from the PDF navigation bypass.
SI-2 mandates timely flaw remediation, such as applying the Chrome update to version 146.0.7680.71 or later, to correct the specific vulnerability and prevent exploitation.
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.AA-05 directly enforces policy-based access management and least privilege, eliminating most improper-access-control defects, yet CWE-284 also covers implementation flaws and design gaps outside a single management control.
Hardened baselines and deviation monitoring directly eliminate most configuration-induced access-control defects, yet CWE-284 also encompasses code-level and design flaws outside the scope of configuration management alone.
Secure SDLC practices catch most access-control defects during design/coding/testing (mostly), yet leave residual risk from runtime configuration, architecture, and operational controls (partial).
PR.AA-01 supplies managed identities/credentials that support but do not implement access-control decisions, so it only partially prevents CWE-284 in either direction.
Authentication directly blocks unauthenticated actors (partial prevention of CWE-284) but leaves authorization logic, policy enforcement, and role checks untouched, so the control neither eliminates nor fully mitigates the broader weakness.
PR.DS-01 encryption mitigates impact of failed access checks on stored data but neither implements nor constrains access-control logic itself.
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.
Defining and enforcing explicit access rights and restrictions for each entity directly stops the assignment of permissions that exceed what is required, eliminating the root condition that allows improper access control.
Formal authorization, role-based provisioning, and timely revocation of access rights directly stop the creation of accounts or permissions that exceed what the business actually needs.
By enforcing explicit rules on which identities or groups may perform read, write, delete or execute operations and by denying anonymous access to sensitive data, the control directly stops the creation of overly permissive or missing access-control checks.
Requiring one-to-one mapping of identities to entities and timely removal of unused identities directly stops attackers from leveraging stale or shared accounts to bypass access restrictions.
By explicitly transferring security roles and responsibilities when personnel change jobs or leave, the control reduces the chance that former employees retain access rights they no longer need, thereby limiting improper access control.
Physical entry controls enforce explicit authorization and authentication at every access point, directly stopping unauthorized actors from reaching information-processing assets.