Skip to main content
Menu
CVEs

Go Vikunja API information disclosure in overdue task webhook payloads

Only affects Vikunja 2.2.0 through 2.7.x with webhooks enabled, where an authenticated user has a personal tasks.overdue webhook. Fixed in 2.8.0.

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

5.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 2.8.0
Who is exposed
Specific setups only

Summary

Written by a model

Vikunja from 2.2.0 before 2.8.0 contains an information disclosure vulnerability that allows authenticated users to read other users' private projects through the tasks.overdue webhook payload. Attackers can register a personal tasks.overdue webhook with one subscribed overdue task, then receive project titles, descriptions, and owner IDs from other users' reminders at external URLs.

Who should check

Teams running Vikunja 2.2.0 through 2.7.x with user-level tasks.overdue webhooks enabled, and anyone shipping the go-vikunja/api Go module (code.vikunja.io/api)

“Affected versions >= 2.2.0, <= 2.7.1”

github.com

What to do

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

    Vikunja versions 2.2.0 through 2.7.x (before 2.8.0) with webhooks enabled Attacker has a personal tasks.overdue webhook and at least one overdue task they are subscribed to
  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-134281 (Vikunja 2.2.0 before 2.8.0 Information Disclosure via tasks.overdue 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-134281 (entry last updated 2026-11-21):
Affected:
- Go package code.vikunja.io/api: from 2.2.0, fixed in 2.8.0
Fixed versions: 2.8.0.
Conditions (all must be true for the bug to be hit):
- Vikunja versions 2.2.0 through 2.7.x (before 2.8.0) with webhooks enabled (source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-pp3p-qw5m-rgm2)
- Attacker has a personal tasks.overdue webhook and at least one overdue task they are subscribed to (source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-pp3p-qw5m-rgm2)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134281 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134281 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-pp3p-qw5m-rgm2
- https://www.vulncheck.com/advisories/vikunja-2.2.0-before-2.8.0-information-disclosure-via-tasks-overdue-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-134281
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-134281"}.

Affected versions

cve.now Index

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

What would change the score

  • Would score about 73 if added to CISA KEV
  • Would score about 68 if CISA's SSVC rates exploitation active
  • Would score about 30 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-pp3p-qw5m-rgm2
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134281
RecordNVD · CVE-2026-134281
Other links 1
Linkvulncheck.com · advisories/vikunja-2.2.0-before-2.8.0-information-disclosure-via-tasks-overdue-webhook-payload

Questions about CVE-2026-134281

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

Authenticated users can read titles, descriptions, identifiers and owner IDs of other users' private projects, including projects they cannot access, and send them to external URLs.

Source: github.com

Which versions are affected by CVE-2026-134281?

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

Source: cve.now feed data

Am I affected, and how do I check?

Vikunja versions 2.2.0 through 2.7.x (before 2.8.0) with webhooks enabled. The setup also requires a personal tasks.overdue webhook with at least one overdue task the webhook owner is subscribed to. Check the installed Vikunja version and whether webhooks are enabled on the instance.

Source: github.com

How do I fix CVE-2026-134281?

Upgrade Vikunja to version 2.8.0 or later, which is the fixed version.

Source: github.com

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