CVE-2026-94445

8.8

golang.org · x/playground

A vulnerability in the golang.org/x/playground component allows unauthenticated remote attackers to achieve arbitrary file writes and potential remote code execution on the host system.

Executive summary

A critical security flaw in golang.org/x/playground allows unauthenticated remote attackers to execute arbitrary code on the host system, posing a severe risk to independent deployments.

Vulnerability

The vulnerability stems from improper input validation where a malicious txtar file can escape the execution context to perform arbitrary file writes, combined with an insecure go vet invocation that permits unauthorized access to environment configurations. These flaws allow an unauthenticated attacker to achieve remote code execution on the underlying host.

Business impact

The exploitation of this vulnerability leads to full system compromise of the playground host, allowing attackers to read sensitive configuration files and execute arbitrary commands. With a CVSS score of 8.8, this high-severity vulnerability presents a significant risk to the integrity and availability of any infrastructure hosting independent instances of the playground.

Remediation

Immediate Action: Administrators must update their golang.org/x/playground deployment to the version containing the fix, identified as 0.0.0-20260924211604-6d73cff14c17.

Proactive Monitoring: Security teams should audit system logs for unexpected file write operations or unusual go vet process activity originating from the playground environment.

Compensating Controls: Ensure the playground service is running within a heavily restricted, isolated container environment with minimal filesystem permissions to mitigate the impact of sandbox escapes.

Exploitation status

Public Exploit Available: No

Analyst recommendation

Given the potential for remote code execution, this vulnerability should be treated with high priority by all organizations maintaining independent deployments of the Go playground. Immediate application of the patched version is required to eliminate the risk of host compromise.

More golang.org CVEs

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources

Originally found and disclosed by splitline (@splitline) from DEVCORE Research Team, per the CVE Program record.