cve.bz

CVE-2026-76019 google chrome: Incorrect Authorization

8.1 highEPSS 0.3%

High (8.1) in google chrome. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
Incorrect authorization in Workers in Google Chrome prior to 151.0.7922.173 allowed a remote attacker who had compromised the renderer process and leveraged social engineering to bypass web origin policy via a crafted HTML page. (Chromium security severity: High)

Severity

CVSS 3.1

8.1 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 27th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-08-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-863 Incorrect Authorization
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-76019 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-76019?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-76019?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-76019 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Google Chromefrom 151.0.7922.173 before 151.0.7922.173

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12chromium151.0.7922.173-1~deb12u1DEBIAN-CVE-2026-76019
Debian13chromium151.0.7922.173-1~deb13u1DEBIAN-CVE-2026-76019
Debian14chromium151.0.7922.173-1DEBIAN-CVE-2026-76019
openSUSELeap 16.0chromium151.0.7922.173-bp160.1.1openSUSE-SU-2026:21624-1
openSUSETumbleweedchromium151.0.7922.173-1.1openSUSE-SU-2026:11581-1

From the distributions' data via OSV.dev: the Debian Security Tracker; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · openSUSE.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as an Important severity flaw because an attacker who bypasses origin restrictions can compromise sensitive cross-origin session data, even though exploitation requires a multi-stage attack involving prior renderer compromise and user interaction. Chromium is not distributed in core Red Hat Enterprise Linux repositories and is only available through community channels such as EPEL and Fedora, which significantly limits exposure across standard enterprise deployments. Typical server environments running without graphical desktop environments or browser installations are unaffected.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-76019.

References

Check your stackJSON