Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-111926 Overview
Coder versions from 2.10.0 before 2.34.8 expose an unauthenticated agent debug HTTP server on 127.0.0.1:2113. The /debug/manifest handler returns the full agent manifest, including template-provided environment variable values. Any lower-privileged Unix user or process running in the same workspace can query this endpoint and read sensitive credentials such as cloud keys or registry tokens. The flaw is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
Critical Impact
Local users sharing a Coder workspace can retrieve cloud credentials, registry tokens, and other secrets passed as environment variables without authentication.
Affected Products
- Coder versions 2.10.0 through 2.34.7
- Coder workspaces running the vulnerable agent binary
- Deployments using template-provided environment variables for secrets
Discovery Timeline
- 2026-10-17 - CVE-2026-111926 published to NVD
- 2026-10-19 - Last updated in NVD database
Technical Details for CVE-2026-111926
Vulnerability Analysis
The Coder agent process binds a debug HTTP server to the loopback interface at 127.0.0.1:2113. This endpoint lacks authentication and exposes a /debug/manifest route intended for diagnostics. The handler returns the complete agent manifest serialized as JSON, which includes every environment variable supplied by the workspace template.
Coder workspaces frequently receive cloud credentials, container registry tokens, and API keys through these template-provided environment variables. The debug endpoint makes these secrets reachable by any process that can open a TCP connection to the loopback interface. Standard Unix process isolation does not block loopback access, so unprivileged users in the same workspace container or VM can retrieve the manifest.
Root Cause
The debug HTTP server was shipped without authentication or access control checks on the /debug/manifest handler. Secrets passed through environment variables were serialized into the manifest response rather than filtered out. The loopback bind address was treated as a sufficient security boundary, which is incorrect in multi-user workspace environments.
Attack Vector
Exploitation requires local access to the workspace with the ability to initiate outbound TCP connections. An attacker running as a lower-privileged Unix user issues an HTTP GET to http://127.0.0.1:2113/debug/manifest using any available HTTP client such as curl or wget. The response body contains the manifest, including environment variable key-value pairs. The attacker then parses the JSON to extract credentials.
No exploit code is published in a public PoC repository at this time. See the GitHub Security Advisory GHSA-73wg-wxvv-9r4j and the VulnCheck Advisory on Coder for additional context.
Detection Methods for CVE-2026-111926
Indicators of Compromise
- Unexpected HTTP connections from non-agent processes to 127.0.0.1:2113 inside Coder workspaces
- Access log entries or audit records showing requests to the /debug/manifest path
- Use of credentials from workspace environment variables originating from unexpected source IPs or user accounts outside the normal workflow
Detection Strategies
- Monitor workspace process telemetry for curl, wget, or scripted HTTP clients targeting the agent debug port
- Audit shell history and process execution records in multi-tenant workspaces for connections to port 2113
- Correlate downstream cloud API calls with the identities and timestamps of workspace sessions to spot credential reuse
Monitoring Recommendations
- Enable network flow logging on workspace hosts to capture loopback traffic to port 2113
- Alert on cloud provider access patterns inconsistent with the user assigned to a given workspace
- Rotate workspace-scoped credentials and track their usage with short-lived token issuance where feasible
How to Mitigate CVE-2026-111926
Immediate Actions Required
- Upgrade Coder to version 2.34.8 or later across all deployments running vulnerable agent builds
- Rotate any cloud keys, registry tokens, and API credentials that were ever passed as environment variables to affected workspaces
- Audit multi-user workspaces for signs of unauthorized access to the /debug/manifest endpoint
Patch Information
Coder resolved the issue in version 2.34.8. Review the GitHub Security Advisory GHSA-73wg-wxvv-9r4j for upgrade guidance and version-specific details.
Workarounds
- Restrict workspace templates to single-user models so no lower-privileged accounts share the agent process
- Deliver secrets through short-lived credential brokers or external secret stores instead of template-provided environment variables
- Use host-level firewall rules inside the workspace to block non-agent processes from reaching 127.0.0.1:2113 where feasible
# Verify running Coder agent version and confirm upgrade
coder version
# Expected: v2.34.8 or later
# Confirm the debug endpoint is no longer exposing manifest secrets
curl -s http://127.0.0.1:2113/debug/manifest | head
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

