CVE-2026-105570: Docker Sandboxes OAuth response masking could be bypassed with a case-variant token host
Docker Sandboxes compared OAuth token-endpoint hostnames case-sensitively when deciding whether to mask managed credential responses, while request routing treated DNS hostnames case-insensitively. Untrusted code inside a sandbox could use a case-variant hostname to reach the genuine provider endpoint while bypassing response masking. If a user completed the OAuth flow, the provider's access and refresh tokens could be returned unmasked to the sandbox, exposing host-managed credentials.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Docker Sandboxesto a version that resolves this vulnerability.Fixed in 0.47.0
Event History
Frequently Asked Questions
Who is exposed to this issue?
Users are exposed when untrusted code runs inside a Docker Sandbox and a user completes an OAuth flow involving managed credentials. In that situation, the sandbox could receive the provider's access and refresh tokens without masking.
What does an attacker need to do to exploit it?
The attacker needs the ability to run untrusted code in a sandbox and issue an OAuth token-endpoint request using a case-variant form of the genuine provider hostname. DNS routing treats the hostname as equivalent, but the masking decision did not.
Are host-managed credentials at risk?
Yes. A successful bypass can expose access and refresh tokens associated with host-managed credentials to code running in the sandbox.