CVE-2026-17749 in the critical feed json
Insufficient validation of untrusted input in Extensions in Google Chrome prior to 151.0.7922.72 allowed an attacker who convinced a user t…
published 3mo ago modified 16d ago also EUVD-2026-50699
- cvss
- 9.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 18%
- public exploits
- 0
- none known
Summary
Insufficient validation of untrusted input in Extensions in Google Chrome prior to 151.0.7922.72 allowed an attacker who convinced a user to install a malicious extension to potentially perform a sandbox escape via a crafted Chrome Extension. (Chromium security severity: Medium)
Patch / fix
- google chrome 151.0.7922.72
- chromium Debian 12 151.0.7922.71-1~deb12u1
- chromium Debian 13 151.0.7922.71-1~deb13u1
- chromium Debian 14 151.0.7922.71-1
debian advisories DEBIAN-CVE-2026-17749
- chromium openSUSE Leap 16.0 151.0.7922.173-bp160.1.1
- chromium openSUSE Tumbleweed 151.0.7922.71-1.1
opensuse advisories openSUSE-SU-2026:21624-1openSUSE-SU-2026:11434-1
Is CVE-2026-17749 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-17749 updated cvss 8.6
chromium-browser: chromium-browser: Insufficient validation of untrusted input in Extensions
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 3mo ago
Exploit prediction
0.26% chance of exploitation in the next 30 days, higher than 18% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 9.6 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H |
| CNA | 3.1 | 9.6 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H |
Affected products
- Google Chrome
Classification
- Weakness
-
- CWE-20 Improper Input Validation
- Technology feeds
References
-
chromereleases.googleblog.com
/2026/07/stable-channel-update-for-desktop_0887107924.html
release-notes, vendor-advisory
-
issues.chromium.org
/issues/500526602
permissions-required
Sources
- CVE List CVE-2026-17749
- NVD CVE-2026-17749
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.