cve.bz

CVE-2026-113286 google chrome: Missing Authorization

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
Missing authorization in Google Lens in Google Chrome prior to 156.0.8078.47 allowed a remote attacker who had compromised the renderer process and leveraged social engineering to leak sensitive information via a crafted HTML page. (Chromium security severity: Low)

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; 28th 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-862 Missing Authorization
OWASP Top 10
A01:2025 Broken Access Control
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-113286 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-113286?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-113286?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-113286 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-113286
Debian13chromium156.0.8078.47-1~deb13u1DEBIAN-CVE-2026-113286
Debian14chromium156.0.8078.47-1DEBIAN-CVE-2026-113286
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

Red Hat Product Security rates this vulnerability as Important severity because it allows an unauthenticated remote attacker to achieve arbitrary code execution upon convincing a user to open a crafted webpage, whereas a lower rating would not reflect the potential for full renderer compromise. Chromium packages are delivered exclusively via Fedora and EPEL community channels rather than core Red Hat Enterprise Linux releases, significantly limiting exposure across enterprise environments. Although the flaw permits code execution within the browser's unprivileged process, standard sandboxing restricts direct access to the underlying operating system unless chained with a separate sandbox escape flaw.

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

Attack patterns (CAPEC)

  • CAPEC-665 Exploitation of Thunderbolt Protection Flaws Likelihood: Low · Severity: Very High

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

References

Check your stackJSON