2025-11 · 2025-Q4
CrewAI "Uncrew" GitHub Token Exposure
Primary layerL1 Credential
Should this run hold this key at all?
- Fixable
- Vendor patch
- Vendor response
- Patched
- In the wild
- No
- Actor
- Attacker
Target
CrewAI platform
Impact
Single internal GitHub token with admin rights to all private repos exposed; CVSS 9.2
Root cause
Improper error handling exposed internal GitHub token
Sources
Catalog
Cite this: AgentProv incident record: CrewAI "Uncrew" GitHub Token Exposure (2025-11). https://agentprov.com/incidents/2025-11-crewai-uncrew-github-token-exposure
Related
- Also L1 · 2026-10-21LiteLLM 1.107.0 on PyPI and Docker Ships a Credential Stealer That Runs at Every Python StartupL1Credential
- Also L1 · 2026-10-17OpenCode Console Breach Exposes Users' Stored OpenAI, Anthropic, and Google API KeysL1Credential
- Also L1 · 2026-10-13IBM MCP Context Forge Shipped a Known JWT Secret, Letting Anyone Mint Platform Admin Tokens (CVE-2026-53709)L1Credential