CVE-2026-8013: Insufficient validation of untrusted input in FedCM in Google Chrome prior to 148.0.7778.96 allowed a remote a

Q: How do I fix CVE-2026-8013?

chrome: upgrade to 148.0.7778.96. Exact commands for each OS are on this page.

Q: Is CVE-2026-8013 being exploited?

CVE-2026-8013 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-8013 affect?

CVE-2026-8013 affects chrome. Severity is medium (CVSS 4.3). Insufficient validation of untrusted input in FedCM in Google Chrome prior to 148.0.7778.96 allowed a remote attacker to leak cross-origin data via a crafted HTML page. (Chromium security severity: Low)

Q: How urgent is CVE-2026-8013?

Priority 16/100. No elevated risk signals yet.

Routine

MEDIUM 4.3UPGRADE

CVE-2026-8013 is a medium-severity flaw (CVSS 4.3) affecting chrome. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Insufficient validation of untrusted input in FedCM in Google Chrome prior to 148.0.7778.96 allowed a remote attacker to leak cross-origin data via a crafted HTML page. (Chromium security severity: Low)

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.2% (top 95%)
CISA exploited list	No
Weakness	CWE-20
Published	2026-05-06
Last modified	2026-10-26

Publisher (CNA): Chrome · Vendor: google

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-05-06 19:16 UTCPublished CVE record published
2026-10-26 19:10 UTCUpdated Record last modified

google chrome UPGRADE

Affected: < 148.0.7778.96

Fixed in: 148.0.7778.96

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy chrome || rpm -q chrome || chrome --version

2. UPGRADE to 148.0.7778.96 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade chrome

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade chrome

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-8013?

chrome: upgrade to 148.0.7778.96. Exact commands for each OS are on this page.

Is CVE-2026-8013 being exploited?

CVE-2026-8013 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-8013 affect?

CVE-2026-8013 affects chrome. Severity is medium (CVSS 4.3). Insufficient validation of untrusted input in FedCM in Google Chrome prior to 148.0.7778.96 allowed a remote attacker to leak cross-origin data via a crafted HTML page. (Chromium security severity: Low)

How urgent is CVE-2026-8013?

Priority 16/100. No elevated risk signals yet.

Software pages

Google Chrome vulnerabilities · Chromium vulnerabilities

Related CVEs

CVE-2026-6296 CRITICAL 9.6 UPGRADE Heap buffer overflow in ANGLE in Google Chrome prior to 147.0.7727.101 allowed a remote attacker to potentiall
CVE-2026-5272 HIGH 8.8 UPGRADE Heap buffer overflow in GPU in Google Chrome prior to 146.0.7680.178 allowed a remote attacker to execute arbi
CVE-2026-5287 HIGH 8.8 UPGRADE Use after free in PDF in Google Chrome prior to 146.0.7680.178 allowed a remote attacker to execute arbitrary
CVE-2026-5289 CRITICAL 9.6 UPGRADE Use after free in Navigation in Google Chrome prior to 146.0.7680.178 allowed a remote attacker who had compro
CVE-2026-5274 HIGH 8.8 UPGRADE Integer overflow in Codecs in Google Chrome prior to 146.0.7680.178 allowed a remote attacker to perform arbit

References

← Back to latest CVEs