Skip to content
Fencer Intel
medium 4.3

CVE-2026-17829 json

Insufficient policy enforcement in Passwords in Google Chrome prior to 151.0.7922.72 allowed a remote attacker to leak cross-origin data vi…

published 3mo ago modified 17d ago also EUVD-2026-50578

cvss
4.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 11%
public exploits
0
none known

Summary

Insufficient policy enforcement in Passwords in Google Chrome prior to 151.0.7922.72 allowed a remote attacker to leak cross-origin data via a crafted HTML page. (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-17829

  • 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-17829 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 Fencer

Vendor 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-17829 updated cvss 6.5

chromium-browser: chromium-browser: Insufficient policy enforcement in Passwords

  • Red Hat All currently supported Red Hat products
    not 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
partial
Assessed
3mo ago

Exploit prediction

0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CISA ADP 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
CNA 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N

Affected products

  • Google Chrome

Classification

Weakness
Technology feeds

References

Sources

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.