Threats / Google / CVE-2022-3038
CVE-2022-3038
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Google Chromium Network Service vulnerability
Use-after-free vulnerability in Chromium Network Service allows remote attackers to exploit heap corruption through crafted HTML, affecting Chrome, Edge, and other Chromium-based browsers.
Verdict
Today item — known-exploited.
Remote attacker crafts malicious HTML to trigger use-after-free in network service memory management, potentially achieving code execution or denial of service on victim systems running vulnerable Chromium browsers.
CISA KEV Yes · 2023-03-304EPSS 0.24738 (verify live)5CVSS 8.8 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreReported 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 2023-03-30).
Probability (EPSS)
EPSS 0.24738 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) · Affected: Google, Chromium Network Service. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-416 Use After Free — weakness family: Memory safety.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 185 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution 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 board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious HTML page that triggers improper memory handling in the Chromium Network Service.
Business
User visits attacker-controlled or compromised website and browser crashes or becomes compromised.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I exploit the use-after-free condition to corrupt heap memory and gain control of execution flow.
Business
Attacker achieves arbitrary code execution within browser process, enabling data theft or malware installation.
3
Lateral reach — past segmentation narrative 3
Attacker
I distribute the malicious HTML through phishing, watering hole attacks, or ad networks to reach target users.
Business
Large-scale compromise of user systems across multiple organizations using Chromium-based browsers.
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