CVE-2022-3038 [Exploited] | Google CHROME Use-After-Free

CVE-2022-3038 is rated Critical Active Threat (89.1/100): CVSS High severity, with high exploitation likelihood (EPSS 35.99%, 97th percentile). CISA KEV confirms active exploitation (added 2023-03-30) affecting Google / Chromium Network Service. a weakness (CWE-416) Unauthenticated remote administrative access may be possible. The CISA remediation deadline has passed—treat as an emergency patch priority.

EDB-ID	Source	Kind	Published	Link
—	nvd_ref	exploit_tag		Exploit-DB ↗

EDB-ID

Source

Kind

Published

Link

—

nvd_ref

exploit_tag

Exploit-DB ↗

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2025-12-24	46.55%	35.99%	-10.56%
2	2025-11-21	5.22%	46.55%	+41.33%
3	2025-11-18	—	5.22%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2025-12-24

46.55%

35.99%

-10.56%

2025-11-21

5.22%

46.55%

+41.33%

2025-11-18

—

5.22%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
8.8	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	2.8	5.9	[email protected]
8.8	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	2.8	5.9	134c704f-9b21-4f2e-91b3-4a467353bcc0

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

8.8

3.1

HIGH

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

2.8

5.9

[email protected]

8.8

3.1

HIGH

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

2.8

5.9

134c704f-9b21-4f2e-91b3-4a467353bcc0

OS Trackers for CVE-2022-3038

vendor	priority	summary	link
`alpine`	—	CVE-2022-3038: 1 source package rows (qt5-qtwebengine); 7 state rows across 7 repos (3.17-community, 3.18-community, 3.19-community, 3.20-community, 3.21-community, 3.22-community, edge-community); fixed 7, open 0.	https://security.alpinelinux.org/vuln/CVE-2022-3038
`debian`	not yet assigned	CVE-2022-3038 not yet assigned priority: Debian including 1 source packages (chromium), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2022-3038
`gentoo`	high	CVE-2022-3038: 1 GLSA(s) (202209-23), 4 atom(s) (www-client/chromium, www-client/chromium-bin, www-client/google-chrome, www-client/microsoft-edge); latest impact high.	https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2022-3038
`ubuntu`	medium	CVE-2022-3038 medium priority: Ubuntu including 1 source packages (chromium-browser), 7 status rows across 7 suites (bionic, focal, jammy, kinetic, trusty, upstream, xenial): DNE 2, not-affected 2, released 2, ignored 1.	https://ubuntu.com/security/CVE-2022-3038

Affected software / configurations for CVE-2022-3038

Vendor	Product	Version	Raw CPE
google	chrome	< 105.0.5195.52	cpe:2.3:a:google:chrome::::::::
fedoraproject	fedora	37	cpe:2.3:o:fedoraproject:fedora:37:::::::*

References for CVE-2022-3038

URL	Tags
http://packetstormsecurity.com/files/168596/Google-Chrome-103.0.5060.53-network-URLLoader-NotifyCompleted-Heap-Use-After-Free.html	Third Party Advisory VDB Entry
https://chromereleases.googleblog.com/2022/08/stable-channel-update-for-desktop_30.html	Release Notes Vendor Advisory
https://crbug.com/1340253	Exploit Vendor Advisory
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/T4NMJURTG5RO3TGD7ZMIQ6Z4ZZ3SAVYE/	Mailing List
https://security.gentoo.org/glsa/202209-23	Third Party Advisory
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2022-3038	US Government Resource

URL

CVE-2022-3038

CISA KEV Record for CVE-2022-3038

Public exploit references (Exploit-DB) for CVE-2022-3038

Exploit prediction scoring system (EPSS) score for CVE-2022-3038

Common vulnerability scoring system (CVSS) metrics for CVE-2022-3038

Weakness enumeration for CVE-2022-3038

OS Trackers for CVE-2022-3038

Affected software / configurations for CVE-2022-3038

References for CVE-2022-3038