Follower removal via missing OAuth scope check
Published Sep 20, 2026 · Updated Sep 20, 2026
Authorization bypass in Pixelfed 0.12.0 through 0.12.11 allows remote authenticated users to remove followers with a read-only OAuth token. The accountRemoveFollowById method checks only for an authenticated user before deleting the follower relationship and does not require the follow scope. Exploitation requires a victim-authorized or stolen read-scoped token and can silently alter that victim's follower list.
Summary
What happened
Authorization bypass in Pixelfed 0.12.0 through 0.12.11 allows remote authenticated users to remove followers with a read-only OAuth token. The accountRemoveFollowById method checks only for an authenticated user before deleting the follower relationship and does not require the follow scope. Exploitation requires a victim-authorized or stolen read-scoped token and can silently alter that victim's follower list.
The record
- CVE
- CVE-2026-93960
- Published
- Sep 20, 2026
- Updated
- Sep 20, 2026
- Vendor
- Pixelfed
- Product
- Pixelfed
- Classifications
- CWE-287, CWE-306
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 20, 2026CVE publishedPublication date reported by the CVE source.
- Sep 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.12.0
- Affected versionversion=0.12.1
- Affected versionversion=0.12.10
- Affected versionversion=0.12.11
- Affected versionversion=0.12.2
- Affected versionversion=0.12.3
- Affected versionversion=0.12.4
- Affected versionversion=0.12.5
- Affected versionversion=0.12.6
- Affected versionversion=0.12.7
- Affected versionversion=0.12.8
- Affected versionversion=0.12.9
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Public exploit references
- Upstream issue 6643 proof of conceptfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started