Skip to main content
VulnerabilityPublished

CVE-2026-95292: Google Chrome · Incorrect Authorization

Affects Google ChromeSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.8 Medium : upgrade to 154.0.8037.57 when convenient.

Data as of 12 Nov 2026, 23:25 UTC

CVSS 3.1 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 154.0.8037.57
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade Google Chrome to 154.0.8037.57.

Affected software

ProductAffectedFixed in
GoogleChromeAffected
  • >=154.0.8037.57 <154.0.8037.57
Fixed in
  • 154.0.8037.57

AI-suggested

Users and administrators should update Google Chrome to version 154.0.8037.57 or later to remediate this vulnerability. The vendor has provided an official fix in this release. No additional mitigation steps are specified or required beyond applying the update.

Description

CVE-2026-95292 is an incorrect authorization vulnerability in the Safe Browsing component of Google Chrome versions prior to 154.0.8037.57. This flaw allows a remote attacker to bypass system access restrictions by sending crafted network traffic. The vulnerability has a medium severity rating with a CVSS score of 4.8. Google has released an update in Chrome version 154.0.8037.57 that addresses this issue.

References

Community reviews

Loading reviews…