GPU VulnDB

Database/AI/ML frameworks & serving

Docker Sandboxes: proxy fails open when masking credentials, leaking host OAuth tokens to sandboxed code

CVSS 5.9CVE-2026-101998AI/ML frameworks & servingcurated

Impact

Docker Sandboxes injects host-held credentials into outbound requests from an agent sandbox and masks them in responses so the code inside never sees them. When a response-body read returned data together with an error, affected handlers forwarded the unmasked bytes, so code running inside an authorized sandbox could recover the host's OAuth access and refresh tokens or a derived Anthropic API key. On a fleet that runs agent workloads in these sandboxes, the boundary that was supposed to keep provider credentials outside tenant code does not hold: whoever controls the code in one sandbox can walk away with a long-lived credential and spend against it from anywhere. The record reports no integrity or availability impact and no scope change.

Who can reach it

Code already executing inside an authorized Docker Sandbox - so an operator or tenant who can submit an agent workload, or a prompt-injected agent, not an unauthenticated outsider. The CVSS 4.0 vector given is adjacent-network with low privileges and a passive attack requirement.

What to do

Update Docker Sandboxes to a release that contains the fix and restart the sandbox tooling; the record links only Docker's sandbox documentation and does not name a fixed version, so confirm the version against Docker's own release notes before declaring nodes clean. Treat any credential that was injected into a sandbox during the exposure window as disclosed: rotate the host OAuth tokens and any derived API keys rather than relying on the patch alone.

References

Related entries

All AI/ML frameworks & serving entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.