Link GitHub MCP Exploited: Accessing private repositories via MCP
As they say in the aricle this is not a bug but an architectural design issue.
I a user uses an MCP integration without finer grained control of access e.g. Access specific repo only then everything using that users access is accesible.
This applies to all MCPs that access mixed sensitive and public context.
Like:
- email sending MCPs: malicious payload can send to unwanted recipients (next wave of spam mailing tools)
- CRM and marketing solutions: exfiltration of sensitive contact info
- calendar: can send sensitive data in notification to URL from malicious payload
- email: can read private emails or send email
- ERP: can extract sensitive company info
- search: can expose users personal queries
- browser: can send users sensitive info (CLI access in regular terminal) to remote controlled data collection servers (infected by hackers to evade tracking or shutdown)
etc..
1 Like