CVE-2025-0437 [High] | Out-of-bounds Read in Chrome

CVE-2025-0437 is rated Moderate Risk (44.2/100): CVSS High severity, with low exploitation likelihood (EPSS 0.09%). Review affected assets and schedule remediation.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2025-11-21	0.15%	0.09%	-0.06%
2	2025-11-18	0.08%	0.15%	+0.07%
3	2025-04-15	—	0.08%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2025-11-21

0.15%

0.09%

-0.06%

2025-11-18

0.08%

0.15%

+0.07%

2025-04-15

—

0.08%

—

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]
6.5	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N` 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:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:L) Some sensitive info could get out, but not a total data dump. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	3.9	2.5	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]

6.5

3.1

MEDIUM

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N 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:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

3.9

2.5

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

OS Trackers for CVE-2025-0437

vendor	priority	summary	link
`alpine`	—	CVE-2025-0437: 1 source package rows (qt6-qtwebengine); 2 state rows across 2 repos (3.22-community, edge-community); fixed 2, open 0.	https://security.alpinelinux.org/vuln/CVE-2025-0437
`debian`	end-of-life	CVE-2025-0437 end-of-life priority: Debian including 1 source packages (chromium), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1.	https://security-tracker.debian.org/tracker/CVE-2025-0437
`gentoo`	high	CVE-2025-0437: 1 GLSA(s) (202507-07), 4 atom(s) (www-client/chromium, www-client/google-chrome, www-client/microsoft-edge, www-client/opera); latest impact high.	https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2025-0437

Affected software / configurations for CVE-2025-0437

Vendor	Product	Version	Raw CPE
google	chrome	< 132.0.6834.83	cpe:2.3:a:google:chrome::::::::

References for CVE-2025-0437

URL	Tags
https://chromereleases.googleblog.com/2025/01/stable-channel-update-for-desktop_14.html	Release Notes
https://issues.chromium.org/issues/378623799	Permissions Required

URL

CVE-2025-0437

Exploit prediction scoring system (EPSS) score for CVE-2025-0437

Common vulnerability scoring system (CVSS) metrics for CVE-2025-0437

Weakness enumeration for CVE-2025-0437

OS Trackers for CVE-2025-0437

Affected software / configurations for CVE-2025-0437

References for CVE-2025-0437