Skip to content
Server Security Center
KEVcritical9.6

CVE-2024-5274: Google Chromium V8 Type Confusion

Google Chromium V8 · listed in the CISA catalog of actively exploited vulnerabilities since 2024-05-28.

CVSS v3.1 (CVE record)
9.6
critical
EPSS (exploit probability, 30 days)
7.7%
higher than 94.7% of all CVEs
Added to CISA KEV
2024-05-28
US federal due date 2024-06-18
Ubuntu priority
–

CVE-2024-5274 explained

CVE-2024-5274 is a type confusion flaw in the V8 JavaScript engine used by Chromium. A crafted HTML page can let a remote attacker run arbitrary code inside the browser sandbox. CISA lists it as known to be exploited, so systems running the affected chromium package should be updated quickly.

Impact

An attacker who gets a user to open a crafted HTML page can execute arbitrary code inside the browser sandbox. No privileges are needed, attack complexity is low, and the attack works over the network, but user interaction is required. The scope is changed, and confidentiality, integrity and availability impacts are all rated high. CISA lists the flaw as known to be exploited.

Who is affected

The facts list one affected release. Debian 12 (bookworm) is affected through the chromium source package. A fixed version, 125.0.6422.112-1~deb12u1, is available in the standard archive. No Ubuntu releases are listed in the facts.

Written with AI from the data on this page and checked against it automatically.

Official description

Type Confusion in V8 in Google Chrome prior to 125.0.6422.112 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)

CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

CISA notes

Upstream versions (CVE record)

From the CVE record published by the vendor or CVE numbering authority.

  • Google Chrome
    Affected
    • < 125.0.6422.112
    Fixed in
    • 125.0.6422.112

Ubuntu and Debian releases

A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.

What to do

  1. On Debian 12 (bookworm), update the chromium package to 125.0.6422.112-1~deb12u1 or later from the standard archive.
  2. Close and restart all running Chromium instances so the patched code is loaded.
  3. Check that every system with Chromium installed now reports the fixed version.
  4. Follow the Debian security advisory for any further guidance.

Written with AI from the data on this page and checked against it automatically.

Check and fix on a server

Run on each Ubuntu or Debian server. Replace chromium with the source package from the table above.

1. Show installed packages built from the source package, with their versions

dpkg-query -W -f='${binary:Package} ${Version} ${source:Package}\n' | awk '$3=="chromium"'

2. Compare each installed version with the fixed version for your release from the table

I=INSTALLED_VERSION; F=FIXED_VERSION   # replace both
dpkg --compare-versions "$I" lt "$F"; case $? in 0) echo vulnerable ;; 1) echo "fixed or newer" ;; *) echo "check the versions" ;; esac

3. Install the fix

sudo apt update && sudo apt install --only-upgrade $(dpkg-query -W -f='${binary:Package} ${source:Package}\n' | awk '$2=="chromium"{print $1}')

Services keep running the old code until they are restarted – restart the affected service or check with needrestart.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-843 Access of Resource Using Incompatible Type ('Type Confusion')

Questions about CVE-2024-5274

Is this vulnerability being exploited?
Yes. CISA added CVE-2024-5274 to its Known Exploited Vulnerabilities catalog on 2024-05-28. Its required action is to apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. Known ransomware use is listed as unknown.
Do I need to reboot after updating?
A reboot is not required for a browser update. Running Chromium processes keep using the old code until they are closed and started again, so restart the browser after installing the update.
Which Debian version fixes the issue on bookworm?
On Debian 12 (bookworm), the chromium package is fixed in version 125.0.6422.112-1~deb12u1, available from the standard archive.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.