# CVE-2026-16422 — Google Chrome

> As of 2026-07-22, CVE-2026-16422 is a HIGH-severity vulnerability in Google Chrome, CVSS v3.1 7.5, EPSS 0.1% (7.4th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-16422, most recently “Google Chrome 150.0.7871.181/.182 Patches 12 High-Severity Vulnerabilities (CVE-2026-16413 through CVE-2026-16424)”.

**Last updated:** 2026-07-22

## What is CVE-2026-16422?

Insufficient validation of untrusted input in Certificate in Google Chrome on Linux prior to 150.0.7871.182 allowed an attacker in a privileged network position to perform domain spoofing via malicious network traffic. (Chromium security severity: High)

The record classifies CVE-2026-16422 under weakness class [CWE-20](https://intel.threadlinqs.com/cwe/CWE-20). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on integrity. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 99 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 7.5 — HIGH (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **EPSS (FIRST):** 0.1% probability of exploitation in the next 30 days, higher than 7.4% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 6/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-07-21, last modified 2026-07-22

## Is CVE-2026-16422 being exploited?

Weaponised exploit code for CVE-2026-16422 is publicly available. 1 public proof-of-concept repository is tracked for this identifier. It currently carries a trending score of 25 in the Threadlinqs vulnerability feed.

- [trickest/cve](https://github.com/trickest/cve/blob/main/2026/CVE-2026-16422.md) (trickest)

## Affected products and versions

- [Google](https://intel.threadlinqs.com/vendors/google): Chrome

## How to fix CVE-2026-16422

No vendor patch reference has been recorded for CVE-2026-16422 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-16422

1 tracked threat in the Threadlinqs corpus references CVE-2026-16422, either in the campaign’s CVE list or as an indicator on the campaign record.

- [Google Chrome 150.0.7871.181/.182 Patches 12 High-Severity Vulnerabilities (CVE-2026-16413 through CVE-2026-16424)](https://intel.threadlinqs.com/threat/TL-2026-1605) — HIGH · 2026-07-22

## Sources

Enriched from CVE.org, FIRST EPSS, public proof-of-concept repositories. Last verified by Threadlinqs on 2026-10-10.

**Other references**

- [chromereleases.googleblog.com](https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0256605430.html)
- [issues.chromium.org](https://issues.chromium.org/issues/533515002)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-16422
Full detection coverage and IOCs for threats exploiting CVE-2026-16422 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp