The vulnerability stems from Pixelfed's failure to properly implement ActivityPub's follow authorization flow. The code shown in fokus.cool's analysis demonstrates that Pixelfed would create follower relationships locally before receiving Accept activities from remote servers, particularly for accounts that should require manual approval. The ApiV1Controller's follow handling logic is directly responsible for this premature relationship creation, while the FollowerController's sendFollow method enables unauthorized federation of this invalid state. The patch notes mention improvements to 'private account handling' and Accept/Reject follow processing, which aligns with these being the vulnerable areas.