Fetching from the wire…
01
02
03
04
05
06
07
08
Public story · 2026-08-10 · high
Ableton MCP got swept in too, two CVEs followed, and Ahuja's fix is pinning MCP installs to a commit SHA, not a branch.
Why now: Ahuja disclosed the account takeover and its two CVEs on August 9.
An attacker compromised Siddharth Ahuja's GitHub account on August 9, stripping his ownership of Blender MCP and Ableton MCP, Ahuja said.
Blender MCP carries 25,000 stars, Ableton MCP has 2,600. Both install straight from GitHub, so every user who trusted the repo inherited the attacker's access the moment ownership flipped.
GitHub suspended the account during a review, and the attacker kept pushing commits in that window, per Ahuja's account. Two CVEs now track the incident, CVE-2026-10661 and CVE-2026-10662.
Ahuja's fix for other maintainers: pin MCP servers to commit SHAs, not branches. A branch reference lets whoever controls the repo push new code that every downstream install picks up automatically. A SHA pin freezes the exact commit a user installed, so a hijacked branch can't silently swap in malicious code.
The incident is sourced only to Ahuja's own posts, with no independent word yet from GitHub or outside researchers on how the account was breached.
MCP's install model trusts whoever controls the repo at fetch time, not who wrote the code. A 25,000-star project didn't stop this from happening to Blender MCP, and nothing about branch-based installs stops it from happening to the next popular server, until SHA pinning becomes the default install instruction instead of an afterthought.
Each link below shares sources, entities, or timing with this story.
Shared entities / Earlier coverage
Both cover August, CVE, GitHub; earlier August coverage from 2026-08-09.
Shared entity: GitHub / Shared topic / Earlier coverage / Tension
Both cover GitHub; overlapping topics (against, commit, repo, star); earlier GitHub coverage from 2026-07-28.
Shared entities / Shared topic / Earlier coverage
Both cover CVE, GitHub; overlapping topics (account, commit); earlier CVE coverage from 2026-08-03.
Both cover GitHub, SHAs; overlapping topics (attacker, compromised); earlier GitHub coverage from 2026-05-13.
Shared entities / Earlier coverage / Tension
Both cover August, GitHub; earlier August coverage from 2026-08-08; pushes against this story (vs).
Both cover CVE, GitHub; earlier CVE coverage from 2026-03-20; pushes against this story (against).
Shared entities / Shared topic
Both cover August, GitHub; overlapping topics (against, control).
Shared entity: August / Shared topic / Earlier coverage / Tension
Both cover August; overlapping topics (repo, star); earlier August coverage from 2026-08-07.