CVE-2026-101998: Fail-open response masking in Docker Sandboxes can expose proxy-managed credentials
Docker Sandboxes could fail open while masking credentials in protected proxy responses. When a response-body read returned data together with an error, affected handlers could forward unmasked bytes. Code inside an authorized sandbox could use this to recover host-managed OAuth access and refresh tokens or a derived Anthropic API key intended to remain outside the sandbox.
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
What access does an attacker need to exploit this issue?
The attacker needs the ability to run code inside an authorized Docker Sandbox. The issue is triggered when that code can cause a protected proxy response-body read to return both data and an error.
What information could be exposed?
Unmasked bytes from protected proxy responses may expose host-managed OAuth access tokens, OAuth refresh tokens, or a derived Anthropic API key that was intended to remain outside the sandbox.
How can I tell whether I may be affected?
You may be affected if Docker Sandboxes are configured to inject or proxy host-managed credentials into sandbox workflows. Review sandbox activity and protected proxy response handling for cases where response reads returned data together with an error, as those conditions could have forwarded unmasked content.