CVE-2026-94445: Malicious user input may lead to RCE in golang.org/x/playground
A malicious txtar could escape the intended execution context and force arbitrary writes to the playground host's trusted filesystem.
Disjointly, one of the three possible paths to invoke go vet on the playground host did not correctly restrict the execution environment. This permitted a Go process to make a read for an environment configuration file rooted in the playground host's $HOME.
Together, a well-crafted go env file and the go vet invocation could lead to remote code execution in the playground host itself.
This does not affect users of go.dev/play directly; however, it may affect independent deployments of golang.org/x/playground.
Affected Software
Event History
Frequently Asked Questions
Who is exposed to this issue?
Independent deployments of golang.org/x/playground may be affected. Users of go.dev/play directly are not affected.
What does exploitation require?
An attacker needs to provide a crafted txtar that escapes the intended execution context and causes arbitrary writes to the playground host's trusted filesystem. The attack also relies on a go vet invocation path that does not properly restrict its execution environment, allowing a Go process to read an environment configuration file rooted in the host's $HOME.
What is the resulting impact if the conditions can be combined?
A well-crafted go env file combined with the affected go vet invocation can lead to remote code execution on the playground host itself.