Skip to main content
Menu
CVEs

Go Vikunja API information disclosure in task deletion webhooks

Affects Vikunja 0.17.0 up to, but not including, 2.8.0, where a deleted task has related tasks in private projects the subscriber cannot read. CVSS rates it Low (2.1). Fixed in 2.8.0.

CVE-2026-134280Published November 21, 2026, updated

2.1LowCNA
Exploited
No known exploitation
Fix
Fixed in 2.8.0
Who is exposed
Specific setups only

Summary

Written by a model

Vikunja 0.17.0 before 2.8.0 builds the task.deleted notification and webhook payload, including related tasks, with the deleting user's permissions and sends it to all project subscribers without per-recipient authorization checks. A user subscribed to a project, or owning its webhook, receives full data of related tasks in private projects they cannot read when a task in their project is deleted.

Who should check

Teams running Vikunja 0.17.0 through 2.7.x with project subscriptions or project task.deleted webhooks enabled, including self-hosted instances.

“A user subscribed to a project, or owning its webhook, receives full data of related tasks in private projects they cannot read”

vulncheck.com

What to do

  1. Check whether your setup matches what the bug needs.

    The attacker must be a user subscribed to the project where a task is deleted, or the owner of a webhook on that project. The deleted task must have related tasks in a different project that the recipient cannot access. Affects Vikunja 0.17.0 up to, but not including, 2.8.0.
  2. Upgrade to a fixed version: 2.8.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-134280 (Vikunja 0.17.0 before 2.8.0 Information Disclosure via task.deleted Webhook Payload), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-134280 (entry last updated 2026-11-21):
Affected:
- Go package code.vikunja.io/api: from 0.17.0, fixed in 2.8.0
Fixed versions: 2.8.0.
Conditions (all must be true for the bug to be hit):
- The attacker must be a user subscribed to the project where a task is deleted, or the owner of a webhook on that project. (source: https://www.vulncheck.com/advisories/vikunja-0.17.0-before-2.8.0-information-disclosure-via-task-deleted-webhook-payload)
- The deleted task must have related tasks in a different project that the recipient cannot access. (source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-2cgh-9vgx-r9gg)
- Affects Vikunja 0.17.0 up to, but not including, 2.8.0. (source: https://www.vulncheck.com/advisories/vikunja-0.17.0-before-2.8.0-information-disclosure-via-task-deleted-webhook-payload)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, a user action.
CISA KEV: CVE-2026-134280 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134280 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-2cgh-9vgx-r9gg
- https://www.vulncheck.com/advisories/vikunja-0.17.0-before-2.8.0-information-disclosure-via-task-deleted-webhook-payload
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-134280
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134280"}.

Affected versions

cve.now Index

20Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Affects Go packages
  • Severity2.1/10CVSS 2.1
  • No patch0/5No signal

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active
  • Would score about 27 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · go-vikunja/vikunja · Advisory GHSA-2cgh-9vgx-r9gg
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134280
RecordNVD · CVE-2026-134280
Other links 1
Linkvulncheck.com · advisories/vikunja-0.17.0-before-2.8.0-information-disclosure-via-task-deleted-webhook-payload

Questions about CVE-2026-134280

Is CVE-2026-134280 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?

When a task is deleted, Vikunja sends a task.deleted webhook notification that includes full data for related tasks in private projects the recipient cannot read. A subscriber to the project, or the owner of a webhook on it, can see those tasks' title, description, dates and assignees.

Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-134280?

code.vikunja.io/api (Go): from 0.17.0 before 2.8.0.

Source: cve.now feed data

Am I affected, and how do I check?

Vikunja 0.17.0 up to, but not including, 2.8.0. Exposure requires a deleted task that has related tasks in a different project the recipient cannot access.

Source: vulncheck.com, github.com

How do I fix CVE-2026-134280?

Upgrade to Vikunja 2.8.0, the fixed version named in the advisory.

Source: vulncheck.com, github.com

No corrections so far. Something wrong on this page? Report an error.