Vikunja before 2.7.1 Task Information Disclosure via Kanban Bucket Move Webhook
Vikunja 2.7.0 and earlier, with webhooks enabled (the default), are exposed to a task information disclosure. The fix is in 2.7.1.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.7.1
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected Vikunja versions are 2.7.0 and earlier (<= 2.7.0). Webhooks are enabled (default configuration). Attacker has a webhook on a project they own for task.updated events, and a Kanban view with a bucket in that project.
- Published
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Vikunja before 2.7.1 contains an authorization bypass vulnerability that allows authenticated users to read any task by injecting a crafted task object into a no-op Kanban bucket move. Attackers can set task.id to a victim task and task.project_id to their own project, routing full task contents to their webhook and forging mention notifications.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affected Vikunja versions are 2.7.0 and earlier (<= 2.7.0). Webhooks are enabled (default configuration). Attacker has a webhook on a project they own for task.updated events, and a Kanban view with a bucket in that project.Upgrade to a fixed version: 2.7.1.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- go-vikunja vikunja
fixed in 2.7.1
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123522
Is CVE-2026-123522 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A user with a webhook on a project they own, and a Kanban view with a bucket in that project, can read the title, description and metadata of tasks across the instance, including tasks in projects they cannot access. The same setup can also send forged mention notifications and change which saved-filter views a task appears in.Source: github.com
Which versions are affected by CVE-2026-123522?
vikunja: before 2.7.1.Source: cve.now feed data
Am I affected, and how do I check?
Vikunja 2.7.0 and earlier are affected, provided webhooks are enabled, which is the default configuration. Compare the installed Vikunja version number with 2.7.0 to check whether the release is in the affected range.Source: github.com
How do I fix CVE-2026-123522?
Upgrade Vikunja to 2.7.1 or later. The advisory lists no workaround.Source: github.com