cve.bz

CVE-2026-6307 google chrome: Type Confusion

8.8 highEPSS 0.4%

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

On this page
Type Confusion in Turbofan in Google Chrome prior to 147.0.7727.101 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 38th 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: total, assessed 2026-04-15. 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-843 Access of Resource Using Incompatible Type (Type Confusion)
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-6307 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-6307?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-6307?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-6307 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 147.0.7727.101 before 147.0.7727.101

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12chromium147.0.7727.101-1~deb12u1DEBIAN-CVE-2026-6307
Debian13chromium147.0.7727.101-1~deb13u1DEBIAN-CVE-2026-6307
Debian14chromium147.0.7727.101-1DEBIAN-CVE-2026-6307
openSUSELeap 16.0chromium147.0.7727.137-bp160.1.1openSUSE-SU-2026:20660-1
openSUSETumbleweedchromium147.0.7727.101-1.1openSUSE-SU-2026:10572-1
Alpinev3.24qt6-qtwebengine6.11.0-r4ALPINE-CVE-2026-6307

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

Red Hat

Red Hat rates this Important.

Red Hat's statement

Red Hat Product Security rates the severity of this flaw as determined by the Google Chrome Security Advisory.

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-6307.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • 0xsha/CVE-2026-6307 Harbor Check: matches CVE 67 stars, HTML, created
    Google Chrome CVE-2026-6307 PoC
  • J4ck3LSyN-Gen2/CVE-2026-6307-Longinus Harbor Check: matches CVE 12 stars, Python, created
    CVE-2026-6307 PoC: Longinus - 2 Boundaries in One Bug https://nebusec.ai/research/v8-cve-2026-6307-writeup/)

References

Check your stackJSON