cve.bz

CVE-2026-113230 google chrome

8.8 highEPSS 0.3%

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

On this page
UI misrepresentation in Browser in Google Chrome prior to 156.0.8078.47 allowed a remote attacker leveraging social engineering to spoof UI elements via a crafted HTML page. (Chromium security severity: Medium)

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.3% (unchanged from 0.3% a week ago) estimated probability of exploitation activity in the next 30 days; 29th 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-10-20. 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-451 User Interface (UI) Misrepresentation of Critical Information
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-113230 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-113230?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-113230?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-113230 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 156.0.8078.47 before 156.0.8078.47

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12chromium156.0.8078.47-1~deb12u1DEBIAN-CVE-2026-113230
Debian13chromium156.0.8078.47-1~deb13u1DEBIAN-CVE-2026-113230
Debian14chromium156.0.8078.47-1DEBIAN-CVE-2026-113230
openSUSELeap 16.0chromium156.0.8078.47-bp160.1.1openSUSE-SU-2026:22185-1
openSUSELeap 16.1chromium157.0.8103.38-bp161.1.1openSUSE-SU-2026:22323-1
openSUSELeap 16.1gn0.20260928-bp161.1.1openSUSE-SU-2026:22323-1
openSUSETumbleweedchromium156.0.8078.47-1.1openSUSE-SU-2026:12234-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 with an Important severity because it enables unauthenticated remote code execution with minimal user interaction, though the blast radius is initially restricted to the browser sandbox rather than compromising the host operating system directly. Successful exploitation allows attackers to manipulate active browser sessions and potentially leverage the compromised sandbox process as a foothold for further privilege escalation. Red Hat Enterprise Linux does not include Chromium in default or supported core repositories, limiting exposure primarily to community-supported distributions.

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

Attack patterns (CAPEC)

  • CAPEC-98 Phishing Likelihood: High · Severity: Very High
  • CAPEC-154 Resource Location Spoofing Likelihood: Medium · Severity: Medium
  • CAPEC-163 Spear Phishing Likelihood: High · Severity: High
  • CAPEC-164 Mobile Phishing Likelihood: High · Severity: High
  • CAPEC-173 Action Spoofing Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON