Skip to content
Server Security Center
KEVcritical9.8

CVE-2025-10585: Google Chromium V8 Type Confusion

Google Chromium V8 · listed in the CISA catalog of actively exploited vulnerabilities since 2025-09-23.

CVSS v3.1 (CVE record)
9.8
critical
EPSS (exploit probability, 30 days)
9.0%
higher than 95.3% of all CVEs
Added to CISA KEV
2025-09-23
US federal due date 2025-10-14
Ubuntu priority
–

CVE-2025-10585 explained

CVE-2025-10585 is a type confusion flaw in the V8 JavaScript engine used by Google Chrome and Chromium before 140.0.7339.185. A crafted HTML page can trigger heap corruption. CISA lists it as known to be exploited, so systems running affected Chromium builds should be updated promptly.

Impact

A remote attacker who gets a user's browser to load a crafted HTML page could potentially corrupt heap memory in V8. The CVSS vector rates it as exploitable over the network with low complexity and no privileges. A successful attack can have high impact on confidentiality, integrity and availability within the affected browser. CISA reports exploitation in the wild. Whether it has been used in ransomware is unknown.

Who is affected

The facts cover the Debian chromium source package only. Fixed versions are available in the standard archive for all listed releases. Debian 12 (bookworm) is fixed in 140.0.7339.185-1~deb12u1. Debian 13 (trixie) is fixed in 140.0.7339.185-1~deb13u1. Debian 14 (forky), the testing distribution, is fixed in 140.0.7339.185-1. No Ubuntu release data is included 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 140.0.7339.185 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, 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
    • < 140.0.7339.185
    Fixed in
    • 140.0.7339.185

Also affected (reported by product suppliers)

  • Siemens CADRA
    Affected
    • all versions
    Fixed in
    not stated

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. Identify Debian systems that have the chromium package installed.
  2. Update chromium to the fixed version for your release, such as 140.0.7339.185-1~deb12u1 on bookworm.
  3. Close and restart all running Chromium instances so the patched code is loaded.
  4. Verify the installed version matches or exceeds the fixed version listed for your release.
  5. Because exploitation is known, prioritise this update on systems where users browse untrusted websites.

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 Type Confusion

Questions about CVE-2025-10585

Is this vulnerability being exploited?
Yes. CISA added CVE-2025-10585 to its Known Exploited Vulnerabilities catalog on 2025-09-23, with a US federal due date of 2025-10-14. Whether it has been used in ransomware campaigns is unknown.
Do I need to restart anything after updating?
Yes. Running Chromium processes keep using the old code until they are closed. Restart the browser after the package update so the fixed V8 engine is in use.
Which Chromium version fixes the issue?
Upstream, versions from 140.0.7339.185 are fixed. On Debian, use 140.0.7339.185-1~deb12u1 for bookworm, 140.0.7339.185-1~deb13u1 for trixie and 140.0.7339.185-1 for forky.

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.