Skip to main content
Menu
CVEs

Go Vikunja API denial of service in CalDAV PROPFIND property handling

Vikunja 0.8.0 through 2.7.1 is affected when CalDAV-capable API tokens are used by users with read access to a project. Fixed in 2.8.0.

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

7.1HighCNA
Exploited
No known exploitation
Fix
Fixed in 2.8.0
Who is exposed
Specific setups only

Summary

Written by a model

Vikunja from 0.8.0 before 2.8.0 contains a denial of service vulnerability that allows authenticated project readers to amplify response size by repeating requested properties in CalDAV PROPFIND requests. Attackers can send PROPFIND requests to the dav projects endpoint with hundreds of duplicate calendar-data properties to exhaust server memory, CPU, and bandwidth.

Who should check

Teams running self-hosted Vikunja from 0.8.0 through 2.7.1 where users with project read access can use CalDAV.

“Affecting vikunja >= 0.8.0, < 2.8.0”

vulncheck.com

What to do

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

    Vikunja versions from 0.8.0 through 2.7.1 (fixed in 2.8.0). The attacker must have read access to a project, via a CalDAV-capable API token.
  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-134275 (Vikunja 0.8.0 before 2.8.0 Denial of Service via CalDAV PROPFIND Duplicate Properties), 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-134275 (entry last updated 2026-11-21):
Affected:
- Go package code.vikunja.io/api: from 0.8.0, fixed in 2.8.0
Fixed versions: 2.8.0.
Conditions (all must be true for the bug to be hit):
- Vikunja versions from 0.8.0 through 2.7.1 (fixed in 2.8.0). (source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-25jc-rq67-h3v6)
- The attacker must have read access to a project, via a CalDAV-capable API token. (source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-25jc-rq67-h3v6)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134275 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134275 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-25jc-rq67-h3v6
- https://www.vulncheck.com/advisories/vikunja-0.8.0-before-2.8.0-denial-of-service-via-caldav-propfind-duplicate-properties
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-134275
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-134275"}.

Affected versions

cve.now Index

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

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 32 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-25jc-rq67-h3v6
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134275
RecordNVD · CVE-2026-134275
Other links 1
Linkvulncheck.com · advisories/vikunja-0.8.0-before-2.8.0-denial-of-service-via-caldav-propfind-duplicate-properties

Questions about CVE-2026-134275

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

An authenticated user can send CalDAV PROPFIND requests with repeated properties, which multiply the response size and can exhaust server memory, CPU and bandwidth, causing denial of service.

Source: github.com, vulncheck.com

Which versions are affected by CVE-2026-134275?

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

Source: cve.now feed data

Am I affected, and how do I check?

The affected range is Vikunja 0.8.0 through 2.7.1. The exposed setup involves CalDAV-capable API tokens and users with read access to a project. Compare the installed Vikunja version against this range.

Source: github.com, vulncheck.com

How do I fix CVE-2026-134275?

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

Source: github.com, vulncheck.com

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