CVE-2022-2856

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-2022-2856 is a security flaw in Chrome and other Chromium browsers, the open-source browser that Chrome, Edge, Brave and Opera are built on. Attackers are using a flaw 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 18 Aug 2022.[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 104.0.5112.101.

Description

CISA calls it an insufficient input validation in Google Chromium Intents. In its words: “Google Chromium Intents contains an insufficient validation of untrusted input vulnerability that allows a remote attacker to browse to a malicious website via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.”[1]

The underlying weakness is improper input validation (CWE-20), in MITRE’s list of common software weaknesses.[2]

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

Affected versions

NVD’s record lists these fixed versions: in each line, everything before the version shown is affected.[2]

ProductFixed in
Chrome104.0.5112.101
chrome104.0.5112.101

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

Exploitation

CISA added it to its catalog of known exploited vulnerabilities on 18 Aug 2022. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 8 Sep 2022 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 5%. That’s in the top 9% of the flaws it scores.[4]

CISA assesses it as not automatable: each attack takes some work.

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

Fix

Google has published a fix or advice.[3] CISA’s required action: “Apply updates per vendor instructions.”[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 104.0.5112.101 or later.Fixed in version 104.0.5112.101. 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
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]
The flaw is made public in the National Vulnerability Database, with a severity score of 6.5.[2]
FIRST puts the odds of it being used in attacks in the next 30 days at 5%.[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 improper input validation flaws

  • CVE-2026-93952, Arista VeloCloud Orchestrator: improper input validation ·
  • CVE-2019-1068, Microsoft SQL Server: remote code execution ·
  • CVE-2026-12569, PTC Windchill and FlexPLM: improper input validation ·
  • CVE-2026-34910, Ubiquiti UniFi OS: improper input validation ·
  • CVE-2026-6973, Ivanti Endpoint Manager Mobile (EPMM): improper input validation ·

Added the same day

  • CVE-2022-32894, Apple iOS and macOS: out-of-bounds write ·
  • CVE-2022-32893, Apple iOS and macOS: out-of-bounds write ·
  • CVE-2022-26923, Microsoft Active Directory: domain services privilege escalation ·
  • CVE-2022-22536, SAP products: HTTP request smuggling ·
  • CVE-2022-21971, Microsoft Windows: runtime remote code execution ·

Every Google flaw on CISA’s list · Everything added in August 2022

References

  1. ^ Cybersecurity and Infrastructure Security Agency. “Google Chromium Intents Insufficient Input Validation Vulnerability”. Known Exploited Vulnerabilities Catalog, added 18 Aug 2022.
  2. ^ National Institute of Standards and Technology. “CVE-2022-2856 Detail”. National Vulnerability Database, published 26 Sep 2022.
  3. ^ Google. Advisories and fixes: chromereleases.googleblog.com.
  4. ^ FIRST. “Exploit Prediction Scoring System”. EPSS 0.046, percentile 91.6, 31 Oct 2026.
  5. CVE Program. “CVE-2022-2856”. 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.