CVE-2025-13223: Google Chromium V8 Type Confusion
Google Chromium V8 · listed in the CISA catalog of actively exploited vulnerabilities since 2025-11-19.
- CVSS v3.1 (CVE record)
- 8.8
- high
- EPSS (exploit probability, 30 days)
- 4.9%
- higher than 92.3% of all CVEs
- Added to CISA KEV
- 2025-11-19
- US federal due date 2025-12-10
- Ubuntu priority
- –
CVE-2025-13223 explained
CVE-2025-13223 is a type confusion flaw in the V8 JavaScript engine used by Google Chrome and Chromium. A remote attacker could potentially exploit heap corruption through a crafted HTML page. CISA lists it as a known exploited vulnerability, so patching browsers should be a priority.
Impact
An attacker who gets a user to open a crafted HTML page could corrupt heap memory in the browser. No privileges are needed and the attack works over the network with low complexity. It does require user interaction. Successful exploitation can lead to high impact on confidentiality, integrity and availability within the affected browser process.
Who is affected
The chromium source package is affected in Debian. Debian 12 (bookworm) is fixed in 142.0.7444.175-1~deb12u1 and Debian 13 (trixie) in 142.0.7444.175-1~deb13u1, both in the standard archive. Debian 14 (forky), the Debian testing distribution, is fixed in 142.0.7444.175-1. Every listed release has a fixed version available.
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 142.0.7444.175 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 ChromeAffectedFixed in
- < 142.0.7444.175
- 142.0.7444.175
| Product | Affected | Fixed in |
|---|---|---|
| Google Chrome |
|
|
Also affected (reported by product suppliers)
- Siemens CADRAAffectedFixed in
- all versions
not stated
| Product | Affected | Fixed in |
|---|---|---|
| Siemens CADRA |
| 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.
Debian 14 (forky)·chromium
testing distribution
Fixed: 142.0.7444.175-1
Debian 13 (trixie)·chromium
Fixed: 142.0.7444.175-1~deb13u1
Debian 12 (bookworm)·chromium
Fixed: 142.0.7444.175-1~deb12u1
What to do
- Update the
chromiumpackage to the fixed version for your Debian release. - Close and restart all running Chromium instances so the patched code is loaded.
- Check that every desktop and kiosk system using Chromium has received the update.
- 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" ;; esac3. 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-2025-13223
- Is this vulnerability being exploited?
- Yes. CISA added CVE-2025-13223 to its Known Exploited Vulnerabilities catalog on 2025-11-19, with a US federal due date of 2025-12-10. Whether it has been used in ransomware campaigns is unknown.
- Do I need to reboot after updating?
- A reboot is not required. Chromium must be fully closed and restarted, because running browser processes keep using the old, vulnerable code until they are restarted.
- Is Debian 14 (forky) covered?
- Yes. The Debian testing distribution forky has the fixed version
142.0.7444.175-1. Note that testing is not a stable release.
Written with AI from the data on this page and checked against it automatically.
References
Other advisories
Trackers and catalogs
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.