Instance-wide attachment theft and deletion via authorization bypass
Published Jul 10, 2026 · Updated Jul 10, 2026
Improper authorization in Vikunja before 2.2.1 allows remote attackers with a link-share URL to read or delete all instance attachments. LinkSharing.ReadAll returns share hashes after clearing only passwords, and GetTaskAttachment authorizes the URL task before fetching a sequential attachment ID without checking task ownership. A public link-share URL is enough to enter the chain; cross-project reads need an accessible task, while deletion also needs a disclosed admin share.
Summary
What happened
Improper authorization in Vikunja before 2.2.1 allows remote attackers with a link-share URL to read or delete all instance attachments. LinkSharing.ReadAll returns share hashes after clearing only passwords, and GetTaskAttachment authorizes the URL task before fetching a sequential attachment ID without checking task ownership. A public link-share URL is enough to enter the chain; cross-project reads need an accessible task, while deletion also needs a disclosed admin share.
The record
- CVE
- CVE-2026-56765
- Published
- Jul 10, 2026
- Updated
- Jul 10, 2026
- Vendor
- Vikunja
- Product
- Vikunja
- Classifications
- CWE-639, T1552, T1213
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 10, 2026CVE publishedPublication date reported by the CVE source.
- Jul 10, 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 <2.2.1
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
Public exploit references
- Vendor advisory curl proof of conceptproof of concept · 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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo