LiteLLM: MCP Authentication Bypass via OAuth2 Passthrough Fallback
Auth bypass lets unauthenticated attackers use MCP tools and reach connected services with fabricated bearer tokens.

2 CRIT · 6 HIGH · 2 MED · 2 INFO · THREAT RED · 12 items · Generated in 224s
Auth bypass lets unauthenticated attackers use MCP tools and reach connected services with fabricated bearer tokens.
A shared chat can trick an admin into running code that makes authenticated requests and creates a server-side Function/Tool for RCE.
A low-privilege user can run another user's MCP workflow with that owner's credentials and access connected data.
Authenticated attackers can write files outside the skills directory and possibly gain code execution on vulnerable hosts.
A path traversal bypass can route terminal proxy requests outside allowed paths using terminal credentials and user headers.
If startup init fails, AWS deny/gate rules are skipped and restricted API actions can run unchecked until restart.
An ungated write tool can create persistent tenant-visible content without consent and may trick users into executing embedded DQL.
Privileged users could make LiteLLM read local files through test_connection, exposing secrets on the host.
AI could automate dangling DNS takeovers at scale, increasing disruption risk for critical services and supply chains.
This is a broad security news roundup, not a specific AI security issue with actionable technical details.
Vendor product announcement with no specific vulnerability, exploit, or defensive finding to act on.
A sandbox escape can let a confined app access host resources, weakening isolation and raising local compromise risk.