/

CVE-2026-86121

Severity:

CRITICAL RISK

(9.8)

Missing Authentication (CWE-306) in Cua Computer Server

CVE-2026-86121

Deferred

Vulnerability type

Category:

Missing Authentication

CWE:

CWE-306

Impact:

Unauthenticated Remote Command Execution

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A critical authentication bypass in Cua computer-server can expose administrative command and file-operation endpoints without requiring credentials. When the CONTAINER_NAME environment variable is unset and the service is reachable on TCP port 8000, an unauthenticated attacker may execute shell commands, access files, or open interactive PTY sessions.

Affected context

The vulnerability affects Cua computer-server deployments using versions before 0.3.42 when the CONTAINER_NAME environment variable is not set. The server also binds to all network interfaces by default, which may make its command, file, and PTY endpoints reachable from untrusted networks.

Exploit preconditions

  • Attack surface: Network-accessible Cua computer-server service
  • Required access: No authentication or prior account access is required
  • Trigger point: Requests to command execution, file operation, or interactive PTY endpoints
  • Why exploitation is possible: Authentication enforcement is skipped when the expected environment variable is absent, while the service remains reachable through its network binding

Why this happens

The underlying bug is a missing authentication control caused by treating an optional or unset environment variable as a condition for bypassing access checks. This maps to CWE-306: Missing Authentication for Critical Function, because sensitive administrative operations remain available without verifying the identity of the caller. Binding to all interfaces by default further expands exposure when network-level restrictions are not present.

Potential impact

  • Unauthenticated attackers may execute arbitrary commands in the server environment
  • Attackers could read, modify, or delete accessible files
  • Interactive PTY access may enable persistent control of the runtime
  • Application secrets and sensitive data may be exposed
  • The host or surrounding environment may be used for lateral movement
  • Service integrity, confidentiality, and availability may be compromised

General mitigation guidance

Mitigation generally focuses on making authentication mandatory and reducing network exposure for administrative interfaces.

Common defensive patterns include:

  • Fail closed when required identity or environment configuration is absent
  • Require strong authentication and authorization for command, file, and PTY operations
  • Bind administrative services to trusted interfaces rather than all interfaces by default
  • Restrict access with network policies, firewalls, or private service boundaries
  • Run the service with a dedicated low-privilege account and minimal filesystem permissions
  • Separate interactive administration endpoints from broadly reachable application traffic
  • Treat environment configuration as security-sensitive and validate it at startup

How teams detect issues like this

Organizations commonly detect this class of issue through:

  • Static analysis and code review for conditional authentication checks based on optional environment variables
  • Tests that verify every sensitive endpoint rejects unauthenticated requests
  • Configuration audits for services listening on all interfaces
  • Network scans identifying exposed administrative ports and endpoints
  • Runtime monitoring for unexpected command execution, file access, or PTY creation
  • Policy enforcement requiring authentication and authorization middleware on administrative routes

Automated security testing and code review tools may help identify missing access controls and fail-open behavior.

Sources

SourceLink
github.comgithub.com/trycua/cua
github.comgithub.com/trycua/cua/blob/10a2e71792db/libs/python/computer-server/computer_server/cli.py
github.comgithub.com/trycua/cua/blob/10a2e71792db/libs/python/computer-server/computer_server/main.py
github.comgithub.com/trycua/cua/commit/59cf25c0ec54
github.comgithub.com/trycua/cua/issues/1892
vulncheck.comvulncheck.com/advisories/cua-computer-server-before-0.3.42-unauthenticated-rce-via-desktop-control

Frequently asked

questions

Yes, when the service is network-reachable and authentication is skipped because the CONTAINER_NAME environment variable is unset. Exposure depends on network routing, firewall rules, and deployment boundaries.

No. The described condition permits unauthenticated access to sensitive command, file, and PTY functionality.

Require authentication and authorization unconditionally for all administrative endpoints, fail closed when security configuration is missing, and limit the service to trusted network interfaces.

Use endpoint-level access-control tests, validate security-critical configuration at startup, monitor exposed management ports, and run administrative services with least privilege.

Find out what's already
exploitable in your codebase.