CVE-2026-95362
Google Chrome cross-site request forgery (CSRF)
- Published29 Sept 2026
Description
Cross-site request forgery in DevTools in Google Chrome prior to 154.0.8037.57 allowed a remote attacker leveraging social engineering to bypass web origin policy via a crafted HTML page. (Chromium security severity: Medium)
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HAffected products
Remediation
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-95362 being actively exploited?
CVE-2026-95362 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.21%.
How severe is CVE-2026-95362?
CVE-2026-95362 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 0.21% probability of exploitation.
Which products are affected by CVE-2026-95362?
Affected products include Google Chrome.
How do I fix CVE-2026-95362?
Upgrade affected software to a fixed version, for example Google Chrome 154.0.8037.57 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-95362 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.