CVE-2023-6345

From Exploited flaws, HARD’s guide to the flaws being used in attacks · Checked
This article is about a flaw in Chrome and other Chromium browsers. For every flaw being used in attacks, see Exploited flaws; for Google’s, see Google flaws being used in attacks.

CVE-2023-6345 is a security flaw in Chrome and other Chromium browsers, the open-source browser that Chrome, Edge, Brave and Opera are built on. Attackers can get past a security protection in Chrome and other Chromium browsers. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 30 Nov 2023.[1]

Chrome and other Chromium browsers is in things households have, such as phones, computers, browsers and everyday apps, so the fix matters at home as much as at work. Fixed in version 119.0.6045.199 of Chrome.

Description

CISA calls it a skia integer overflow in Google Chromium Skia. In its words: “Google Chromium Skia contains an integer overflow vulnerability that allows a remote attacker, who has compromised the renderer process, to potentially perform a sandbox escape via a malicious file. This vulnerability affects Google Chrome and ChromeOS, Android, Flutter, and possibly other products.”[1]

The underlying weakness is integer overflow (CWE-190), in MITRE’s list of common software weaknesses.[2]

It scores 9.6 out of 10 on the Common Vulnerability Scoring System, which rates it critical, scored by NVD using CVSS 3.1.[2]

Affected versions

NVD’s record lists one fixed version: everything before it is affected.[2]

ProductFixed in
Chrome119.0.6045.199

Every device with Chrome and other Chromium browsers needs the update.

Exploitation

CISA added it to its catalog of known exploited vulnerabilities on 30 Nov 2023, within a day of it being made public. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 21 Dec 2023 to fix it.[1]

FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at 16%. That’s in the top 4% of the flaws it scores.[4]

CISA assesses it as automatable: attackers can run it against many targets at once.

CISA doesn’t say who was attacked, or how.

Fix

Google has published a fix or advice.[3] CISA’s required action: “Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.”[1]

  1. Update Chrome and other Chromium browsers now.Chrome updates itself, but only finishes when you restart it: open the menu, choose Help, then About Google Chrome, and click Relaunch. Edge, Brave, Opera and Vivaldi need the same. Then turn on automatic updates, so the next fix arrives on its own.
  2. Check you’re on 119.0.6045.199 or later.Fixed in version 119.0.6045.199 of Chrome. Anything older is what attackers are going after.
  3. If there’s no update, stop using it.CISA’s advice when a flaw being used in attacks has no fix is to stop using the product until it does.

Timeline

DateEvent
The flaw is made public in the National Vulnerability Database, with a severity score of 9.6.[2]
CISA adds it to its catalog of flaws known to be used in attacks.[1]
CISA’s deadline for US government agencies to fix it.[1]
FIRST puts the odds of it being used in attacks in the next 30 days at 16%.[4]

See also

Other Chrome and other Chromium browsers flaws

Other Google flaws

  • CVE-2026-111497, Google Brotli: unchecked return value ·
  • CVE-2026-58704, Google Pixel: improper authorization ·
  • CVE-2026-87491, Chrome and other Chromium browsers: out of bounds write ·
  • CVE-2026-85046, Chrome and other Chromium browsers: type confusion ·
  • CVE-2026-11645, Chrome and other Chromium browsers: out-of-bounds read and write ·

Other integer overflow flaws

  • CVE-2026-97229, GitLab Community Edition and Enterprise Edition: integer overflow or wraparound ·
  • CVE-2025-48595, Android Framework: integer overflow ·
  • CVE-2021-30952, Apple devices: integer overflow or wraparound ·
  • CVE-2026-21385, Qualcomm Multiple Chipsets: memory corruption ·
  • CVE-2018-14634, Linux Kernel: integer overflow ·

Added the same day

  • CVE-2023-49103, ownCloud graphapi: graphapi information disclosure ·

Every Google flaw on CISA’s list · Everything added in November 2023

References

  1. ^ Cybersecurity and Infrastructure Security Agency. “Google Skia Integer Overflow Vulnerability”. Known Exploited Vulnerabilities Catalog, added 30 Nov 2023.
  2. ^ National Institute of Standards and Technology. “CVE-2023-6345 Detail”. National Vulnerability Database, published 29 Nov 2023.
  3. ^ Google. Advisories and fixes: chromereleases.googleblog.com.
  4. ^ FIRST. “Exploit Prediction Scoring System”. EPSS 0.165, percentile 97.0, 31 Oct 2026.
  5. CVE Program. “CVE-2023-6345”. The official CVE record.

This article is built from CISA’s catalog (version 2026.10.30), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.