Skip to content
Fencer Vulns
medium 4.3

CVE-2026-79095 json

Information leak in Payments in Google Chrome prior to 152.0.7977.65 allowed a remote attacker to obtain cross-origin data via a crafted HT…

published 2026-08-25 2 mo ago modified 2026-08-28 2 mo ago also EUVD-2026-65871

cvss
4.3
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 17%
public exploits
0
none known

Summary

Information leak in Payments in Google Chrome prior to 152.0.7977.65 allowed a remote attacker to obtain cross-origin data via a crafted HTML page. (Chromium security severity: Medium)

Patch / fix

  • google chrome 152.0.7977.65
  • chromium Debian 12 152.0.7977.75-1~deb12u1
  • chromium Debian 13 152.0.7977.75-1~deb13u1
  • chromium Debian 14 152.0.7977.64-1

debian advisories DEBIAN-CVE-2026-79095

  • chromium openSUSE Leap 16.0 152.0.7977.82-bp160.1.1
  • chromium openSUSE Tumbleweed 152.0.7977.64-1.1

opensuse advisories openSUSE-SU-2026:21799-1openSUSE-SU-2026:11628-1

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-79095 updated cvss 6.5

chromium-browser: Chromium: Information leak in Payments allows remote attackers to obtain cross-origin data

  • 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
2 mo ago

Exploit prediction

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

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
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
Technology feeds

References

Sources

Fencer Vulns 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.