CVE-2025-0291 [High] | Security Vulnerability in Chrome

CVE-2025-0291 is rated High Risk (66.1/100): CVSS High severity, with high exploitation likelihood (EPSS 12.09%, 94th percentile). EPSS ranks this CVE among the most likely to be exploited in the near term. High exploitation likelihood—assess exposure and prioritize remediation.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-03-04	14.02%	12.09%	-1.93%
2	2026-03-01	12.09%	14.02%	+1.93%
3	2026-02-16	—	12.09%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-03-04

14.02%

12.09%

-1.93%

2026-03-01

12.09%

14.02%

+1.93%

2026-02-16

—

12.09%

—

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.3	3.1	HIGH	`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/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:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. 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:C) Breaking this can reach past the original component and bite other resources—bigger blast radius. 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.	1.6	6.0	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.3

3.1

HIGH

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/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:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
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:C): Breaking this can reach past the original component and bite other resources—bigger blast radius.
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.

1.6

6.0

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

OS Trackers for CVE-2025-0291

vendor	priority	summary	link
`debian`	end-of-life	CVE-2025-0291 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-0291
`gentoo`	high	CVE-2025-0291: 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-0291
`ubuntu`	medium	CVE-2025-0291 medium priority: Ubuntu including 1 source packages (chromium-browser), 5 status rows across 5 suites (focal, jammy, noble, oracular, upstream): not-affected 3, DNE 1, released 1.	https://ubuntu.com/security/CVE-2025-0291

Affected software / configurations for CVE-2025-0291

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

References for CVE-2025-0291

URL	Tags
https://chromereleases.googleblog.com/2025/01/stable-channel-update-for-desktop.html	Vendor Advisory
https://issues.chromium.org/issues/383356864	Permissions Required

URL

CVE-2025-0291

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

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

Weakness enumeration for CVE-2025-0291

OS Trackers for CVE-2025-0291

Affected software / configurations for CVE-2025-0291

References for CVE-2025-0291