CVE-2025-3069
published 2025-04-02CVE-2025-3069: Inappropriate implementation in Extensions in Google Chrome prior to 135.0.7049.52 allowed a remote attacker to perform privilege escalation via a crafted HTML…
PriorityP344high8.8CVSS 3.1
AVNACLPRNUIRSUCHIHAH
EPSS
0.32%
24.5th percentile
Inappropriate implementation in Extensions in Google Chrome prior to 135.0.7049.52 allowed a remote attacker to perform privilege escalation via a crafted HTML page. (Chromium security severity: Medium)
Affected
9 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| chromium | chromium | >= 0 < 135.0.7049.52-1~deb12u1 | 135.0.7049.52-1~deb12u1 |
| chromium | chromium | >= 0 < 135.0.7049.52-1 | 135.0.7049.52-1 |
| chromium | chromium | >= 0 < 135.0.7049.52-1 | 135.0.7049.52-1 |
| debian | chromium | < chromium 135.0.7049.52-1~deb12u1 (bookworm) | chromium 135.0.7049.52-1~deb12u1 (bookworm) |
| chrome | < 135.0.7049.52 | 135.0.7049.52 | |
| chrome | >= 135.0.7049.52 < 135.0.7049.52 | 135.0.7049.52 | |
| chrome_chrome | — | — | |
| msrc | microsoft_edge | — | — |
| paloalto | prisma_browser | — | — |
CVSS provenance
nvdv3.18.8HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
osv8.8HIGH
vendor_debian8.8HIGH
vendor_msrc8.8HIGH
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Palo Alto
PAN-SA-2025-0009 Chromium: Monthly Vulnerability Update (May 2025)
vendor_paloalto·2025-05-14·CVSS 8.8
[HIGH] PAN-SA-2025-0009 Chromium: Monthly Vulnerability Update (May 2025)
PAN-SA-2025-0009 Chromium: Monthly Vulnerability Update (May 2025)
Palo Alto Networks incorporated the following Chromium security fixes into our products: https://chromereleases.googleblog.com/2025/05/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2025/04/stable-channel-update-for-desktop_29.html https://chromereleases.googleblog.com/2025/04/stable-channel-update-for-desktop_8.html https://chromereleases.googleblog.com/2025/04/stable-channel-update-for-desktop.html CVE Summary CVE-2025-3066 Use after free in Site Isolation CVE-2025-3067 Inappropriate implementation in Custom Tabs CVE-2025-3068 Inappropriate implementation in Intents CVE-2025-3069 Inappropriate implementation in Extensions CVE-2025-3070 Insufficient validation of untrusted input in Extensions
Red Hat
kernel: drm/xe/vf: Don't try to trigger a full GT reset if VF
vendor_redhat·2025-05-01·CVSS 5.5
CVE-2025-23162 [MEDIUM] CWE-20 kernel: drm/xe/vf: Don't try to trigger a full GT reset if VF
kernel: drm/xe/vf: Don't try to trigger a full GT reset if VF
In the Linux kernel, the following vulnerability has been resolved:
drm/xe/vf: Don't try to trigger a full GT reset if VF
VFs don't have access to the GDRST(0x941c) register that driver
uses to reset a GT. Attempt to trigger a reset using debugfs:
$ cat /sys/kernel/debug/dri/0000:00:02.1/gt0/force_reset
or due to a hang condition detected by the driver leads to:
[ ] xe 0000:00:02.1: [drm] GT0: trying reset from force_reset [xe]
[ ] xe 0000:00:02.1: [drm] GT0: reset queued
[ ] xe 0000:00:02.1: [drm] GT0: reset started
[ ] ------------[ cut here ]------------
[ ] xe 0000:00:02.1: [drm] GT0: VF is trying to write 0x1 to an inaccessible register 0x941c+0x0
[ ] WARNING: CPU: 3 PID: 3069 at drivers/gpu/drm/xe/xe_gt_sriov_vf.c:996 xe_
Chrome
Stable Channel Update for ChromeOS / ChromeOS Flex: CVE-2025-3069
vendor_chrome·2025-04-17·CVSS 8.8
CVE-2025-3069 [HIGH] Stable Channel Update for ChromeOS / ChromeOS Flex: CVE-2025-3069
Stable Channel Update for ChromeOS / ChromeOS Flex
CVE-2025-3069
Microsoft
Chromium: CVE-2025-3069 Inappropriate implementation in Extensions
vendor_msrc·2025-04-08·CVSS 8.8
CVE-2025-3069 [HIGH] Chromium: CVE-2025-3069 Inappropriate implementation in Extensions
Chromium: CVE-2025-3069 Inappropriate implementation in Extensions
Description: This CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information.
FAQ: Why is this Chrome CVE included in the Security Update Guide?
The vulnerability assigned to this CVE is in Chromium Open Source Software (OSS) which is consumed by Microsoft Edge (Chromium-based). It is being documented in the Security Update Guide to announce that the latest version of Microsoft Edge (Chromium-based) is no longer vulnerable.
How can I see the version of the browser?
In your Microsoft Edge browser, click on the 3 dots (...) on the very right-hand side of the window
Click on Help and Feedback
Click on About Microsof
Chrome
Stable Channel Update for Desktop: CVE-2025-3067
vendor_chrome·2025-04-01·CVSS 8.6
CVE-2025-3067 [MEDIUM] Stable Channel Update for Desktop: CVE-2025-3067
Stable Channel Update for Desktop
CVE-2025-3067: Inappropriate implementation in Custom Tabs. Reported by Philipp Beer (TU Wien) on 2024-10-31 [$2000][ 401823929 ] Medium CVE-2025-3068: Inappropriate implementation in Intents
Reported by Simon Rawet on 2025-03-09 [$1000][ 40060076 ] Medium CVE-2025-3069: Inappropriate implementation in Extensions
Severity: medium
Debian
CVE-2025-3069: chromium - Inappropriate implementation in Extensions in Google Chrome prior to 135.0.7049....
vendor_debian·2025·CVSS 8.8
CVE-2025-3069 [HIGH] CVE-2025-3069: chromium - Inappropriate implementation in Extensions in Google Chrome prior to 135.0.7049....
Inappropriate implementation in Extensions in Google Chrome prior to 135.0.7049.52 allowed a remote attacker to perform privilege escalation via a crafted HTML page. (Chromium security severity: Medium)
Scope: local
bookworm: resolved (fixed in 135.0.7049.52-1~deb12u1)
bullseye: open
forky: resolved (fixed in 135.0.7049.52-1)
sid: resolved (fixed in 135.0.7049.52-1)
trixie: resolved (fixed in 135.0.7049.52-1)
OSV
CVE-2025-3069: Inappropriate implementation in Extensions in Google Chrome prior to 135
osv·2025-04-02·CVSS 8.8
CVE-2025-3069 [HIGH] CVE-2025-3069: Inappropriate implementation in Extensions in Google Chrome prior to 135
Inappropriate implementation in Extensions in Google Chrome prior to 135.0.7049.52 allowed a remote attacker to perform privilege escalation via a crafted HTML page. (Chromium security severity: Medium)
GHSA
GHSA-xhmh-cq7j-qhjr: Inappropriate implementation in Extensions in Google Chrome prior to 135
ghsa_unreviewed·2025-04-02
CVE-2025-3069 [HIGH] CWE-358 GHSA-xhmh-cq7j-qhjr: Inappropriate implementation in Extensions in Google Chrome prior to 135
Inappropriate implementation in Extensions in Google Chrome prior to 135.0.7049.52 allowed a remote attacker to perform privilege escalation via a crafted HTML page. (Chromium security severity: Medium)
No detection rules found.
No public exploits indexed.
Bleepingcomputer
Microsoft April 2025 Patch Tuesday fixes exploited zero-day, 134 flaws
blogs_bleepingcomputer·2025-04-08·CVSS 7.8
[HIGH] Microsoft April 2025 Patch Tuesday fixes exploited zero-day, 134 flaws
## Microsoft April 2025 Patch Tuesday fixes exploited zero-day, 134 flaws
## Lawrence Abrams
49 Elevation of Privilege Vulnerabilities
9 Security Feature Bypass Vulnerabilities
31 Remote Code Execution Vulnerabilities
17 Information Disclosure Vulnerabilities
14 Denial of Service Vulnerabilities
3 Spoofing Vulnerabilities
The above numbers do not include Mariner flaws and 13 Microsoft Edge vulnerabilities fixed earlier this month.
To learn more about the non-security updates released today, you can review our dedicated articles on the Windows 11 KB5055523 & KB5055528 cumulative updates and the Windows 10 KB5055518 update .
## One actively exploited zero-days
This month's Patch Tuesday fixes one actively exploited zero-day. Microsoft classifies a zero-day flaw as publicly disclos
Bugzilla
CVE-2025-23162 kernel: drm/xe/vf: Don't try to trigger a full GT reset if VF
bugzilla·2025-05-01·CVSS 5.5
CVE-2025-23162 [MEDIUM] CVE-2025-23162 kernel: drm/xe/vf: Don't try to trigger a full GT reset if VF
CVE-2025-23162 kernel: drm/xe/vf: Don't try to trigger a full GT reset if VF
In the Linux kernel, the following vulnerability has been resolved:
drm/xe/vf: Don't try to trigger a full GT reset if VF
VFs don't have access to the GDRST(0x941c) register that driver
uses to reset a GT. Attempt to trigger a reset using debugfs:
$ cat /sys/kernel/debug/dri/0000:00:02.1/gt0/force_reset
or due to a hang condition detected by the driver leads to:
[ ] xe 0000:00:02.1: [drm] GT0: trying reset from force_reset [xe]
[ ] xe 0000:00:02.1: [drm] GT0: reset queued
[ ] xe 0000:00:02.1: [drm] GT0: reset started
[ ] ------------[ cut here ]------------
[ ] xe 0000:00:02.1: [drm] GT0: VF is trying to write 0x1 to an inaccessible register 0x941c+0x0
[ ] WARNING: CPU: 3 PID: 3069 at drivers/gpu/drm/xe/xe_g
2025-04-02
Published