CVE-2026-3930: Unsafe navigation in Navigation
Chromium: CVE-2026-3930 Unsafe navigation in Navigation
Other sources
This CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information.
— Microsoft
Unsafe navigation in Navigation in Google Chrome on iOS prior to 146.0.7680.71 allowed a remote attacker to bypass navigation restrictions via a crafted HTML page. (Chromium security severity: Medium)
— MITRE
Credit
Affected Software
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2026-3913
- CVE-2026-3914
- CVE-2026-3915
- CVE-2026-3916
- CVE-2026-3917
- CVE-2026-3918
- CVE-2026-3919
- CVE-2026-3920
- CVE-2026-3921
- CVE-2026-3922
- CVE-2026-3923
- CVE-2026-3924
- CVE-2026-3925
- CVE-2026-3926
- CVE-2026-3927
- CVE-2026-3928
- CVE-2026-3929
- CVE-2026-3931
- CVE-2026-3932
- CVE-2026-3934
- CVE-2026-3935
- CVE-2026-3936
- CVE-2026-3937
- CVE-2026-3938
- CVE-2026-3939
- CVE-2026-3940
- CVE-2026-3941
- CVE-2026-3942
Frequently Asked Questions
What is the severity of CVE-2026-3930?
CVE-2026-3930 is classified with a moderate severity level.
How do I fix CVE-2026-3930?
To fix CVE-2026-3930, update Google Chrome to version 146.0.7680.71 or later, or update Microsoft Edge to version 146.0.3856.59 or later.
Which products are affected by CVE-2026-3930?
CVE-2026-3930 affects Google Chrome versions earlier than 146.0.7680.71 and Microsoft Edge versions earlier than 146.0.3856.59.
Who reported CVE-2026-3930?
CVE-2026-3930 was reported by the Chromium team.
Is CVE-2026-3930 specific to any browser?
Yes, CVE-2026-3930 is specifically related to vulnerabilities found in Chromium-based browsers like Google Chrome and Microsoft Edge.