CVE-2022-2856
CVE-2022-2856 is a medium-severity vulnerability (CVSS 3.1 base score 6.5). 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. CISA added it to the Known Exploited Vulnerabilities catalog on 2022-08-18, with a remediation due date of 2022-09-08 for US federal civilian agencies. As of 2026-11-22, EPSS estimates a 4.6% probability of exploitation in the next 30 days, in the 91st percentile of scored CVEs.
Updated
- CVSS 3.1
- 6.5 MEDIUM
- EPSS
- 4.6% (91st pct)
- CISA KEV
- Exploited
- Published
- 2022-09-26
- Weakness
- CWE-20
Google Chromium Intents Insufficient Input Validation Vulnerability is confirmed as actively exploited and is listed in the CISA KEV catalog.
Required action
Apply updates per vendor instructions.
CISA notes
https://chromereleases.googleblog.com/2022/08/stable-channel-update-for-desktop_16.html; https://nvd.nist.gov/vuln/detail/CVE-2022-2856
Description
Insufficient validation of untrusted input in Intents in Google Chrome on Android prior to 104.0.5112.101 allowed a remote attacker to arbitrarily browse to a malicious website via a crafted HTML page.
Key Findings
as of 2026-11-22- CISA added CVE-2022-2856 to the KEV catalog 39 days before its CVE record was published.
- It is one of 77 Google entries in the CISA KEV catalog, and one of 21 added in 2022.
- Its current EPSS score (4.6%) is higher than that of 16% of CISA KEV entries.
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:NOpen in CVSS calculator Remediation Timeline
BOD 26-04, US federal agenciesDeadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (listed) and CISA's SSVC values (automatable no, technical impact partial, 2024-03-26).
How the timeline is set
Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.
Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet.
CISA calculates the KEV due date with the same table, using its own evidence on whether the vulnerability is present in a publicly exposed asset. Each agency makes the final exposure decision for each of its assets.
Affected Products
| Vendor | Product | Affected versions |
|---|---|---|
Google Chrome | unspecified to <104.0.5112.101 |
References
3 linksRecord Details
- Published
- 2022-09-26
- Last updated
- 2025-10-21
- Assigner (CNA)
- Chrome
- Credited to
- -
More from Google
Google Chromium Intents Improper Input Validation Vulnerability
Google Chromium WebP Heap-Based Buffer Overflow Vulnerability
Out-of-Bounds Write in Google Brotli Decoder
Google Chromium V8 Remote Code Execution Vulnerability
CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.