basicsecurity.net
Proof, not just disclosure.
Threats / Google / CVE-2022-2856
CVE-2022-2856 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Google Chromium Intents vulnerability

Insufficient input validation in Chromium Intents allows remote attackers to craft malicious HTML pages that could be used to compromise browsers including Chrome, Edge, and Opera.

Verdict

Today item — known-exploited.

A remote attacker can craft a malicious HTML page exploiting insufficient validation of untrusted input in Chromium Intents. Successful exploitation could lead to unintended navigation or execution of unvalidated intent handlers across multiple Chromium-based browsers.

CISA KEV Yes · 2022-08-183EPSS 0.04493 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
4 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-08-18).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.04493 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Google, Chromium Intents. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-20 Improper Input Validation.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious HTML page with specially formatted intent data that bypasses validation checks.
Business
Users are exposed to phishing, malware distribution, or credential theft through unexpected navigation to attacker-controlled sites.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I host the malicious page and trick users into visiting it through social engineering or compromised legitimate sites.
Business
Browser security boundaries are weakened, affecting user trust in multiple vendors' products simultaneously.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 4 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by Chrome (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by ChromeCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.