CVE-2026-113063: Clickjacking in Chromoting

Q: What would an attacker need to exploit this issue?

An attacker would need to cause a user to process a crafted HTML page. The attack can be performed remotely.

Q: Which Chrome versions should be considered affected?

Google Chrome versions prior to 156.0.8078.47 are affected.

Q: Does the reported code execution extend beyond Chrome's sandbox?

The available information describes potential arbitrary code execution inside the sandbox. It does not state that the vulnerability enables a sandbox escape.

Published Sep 17, 2026

Updated

Chromium CVE-2026-113063: Improper input validation

Other sources

Clickjacking in Chromoting in Google Chrome prior to 156.0.8078.47 allowed a remote attacker leveraging social engineering to spoof UI elements via crafted network traffic. (Chromium security severity: Low)

— NVD

Improper input validation in Chromoting in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Low)

— MITRE

This CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information.

— Microsoft

Credit

Google

Affected Software

8 affected componentsFixes available

Microsoft Edge (Chromium-based)<156.0.4314.42

156.0.4314.42

Microsoft Edge<156.0.4314.42

156.0.4314.42

Google Chrome<156.0.8078.47

156.0.8078.47

Google Chrome<156.0.8078.47

debian/chromium<156.0.8078.47-1~deb12u1

156.0.8078.47-1~deb12u1

debian/chromium<156.0.8078.47-1~deb13u1

156.0.8078.47-1~deb13u1

debian/chromium<156.0.8078.47-1

156.0.8078.47-1

debian/chromium<=150.0.7871.100-1~deb12u1, <=150.0.7871.181-1~deb13u1

156.0.8078.79-1~deb12u1156.0.8078.79-1~deb13u1156.0.8078.79-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 156.0.4314.42
Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 156.0.8078.47
Upgrade
Upgrade debian/chromium to a version that resolves this vulnerability.
Fixed in 156.0.8078.47-1~deb12u1
Upgrade
Upgrade debian/chromium to a version that resolves this vulnerability.
Fixed in 156.0.8078.47-1~deb13u1
Upgrade
Upgrade debian/chromium to a version that resolves this vulnerability.
Fixed in 156.0.8078.47-1
Upgrade
Upgrade debian/chromium to a version that resolves this vulnerability.
Fixed in 156.0.8078.79-1~deb12u1Fixed in 156.0.8078.79-1~deb13u1Fixed in 156.0.8078.79-1
Upgrade
Upgrade Google Chrome to a version that resolves this vulnerability.
Fixed in 156.0.8078.47

Event History

Sep 17, 2026

CVE Published

12:00 AM

Data Sourced

12:00 AM

SeverityWeaknessAffected Software

Oct 20, 2026

CVE Published

via MITRE·09:02 PM

Data Sourced

via MITRE·09:02 PM

DescriptionWeakness

Data Sourced

via NVD·10:18 PM

DescriptionSeverityWeaknessAffected Software

Data Sourced

via OSV·10:18 PM

DescriptionSeverityAffected Software

Oct 23, 2026

Data Sourced

via Microsoft·02:35 AM

DescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

What would an attacker need to exploit this issue?

An attacker would need to cause a user to process a crafted HTML page. The attack can be performed remotely.

Which Chrome versions should be considered affected?

Google Chrome versions prior to 156.0.8078.47 are affected.

Does the reported code execution extend beyond Chrome's sandbox?

The available information describes potential arbitrary code execution inside the sandbox. It does not state that the vulnerability enables a sandbox escape.

CVE-2026-113063: Clickjacking in Chromoting

Other sources

Credit

Affected Software

Remediation

Event History

Parent advisories

Peer vulnerabilities

Frequently Asked Questions

What would an attacker need to exploit this issue?

Which Chrome versions should be considered affected?

Does the reported code execution extend beyond Chrome's sandbox?

Company

Resources

Contact