Go Vikunja API denial of service in datemath business-day filter
- Exploited
- No known exploitation
- Fix
- Fixed in 2.8.0
- Who is exposed
- Specific setups only
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
Original 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.
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
“Vikunja from 0.19.0 before 2.8.0”
What to do
Check whether your setup matches what the bug needs.
Vikunja versions from 0.19.0 before 2.8.0 (the GitHub advisory lists affected versions up to 2.7.1) Task or time-tracking filters that accept datemath business-day operandsUpgrade 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-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"}.Affected versions
cve.now Index
- 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
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · go-vikunja/vikunja · Advisory GHSA-4f8c-84wp-h6q5 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134266 |
| Record | NVD · CVE-2026-134266 |
| Other links 1 | |
| Link | vulncheck.com · advisories/vikunja-0.19.0-before-2.8.0-denial-of-service-via-datemath-business-day-filter |
Questions about CVE-2026-134266
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: cve.now feed data
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: vulncheck.com, github.com
Which versions are affected by CVE-2026-134266?
code.vikunja.io/api (Go): from 0.19.0 before 2.8.0.
Source: cve.now feed data
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: vulncheck.com, github.com
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: vulncheck.com, github.com
Related
- CVE-2026-123531Vikunja 1.0.0 before 2.7.1 Pagination Limit Bypass via page=0 Parameter
- CVE-2026-134282Vikunja 0.14.0 before 2.8.0 Arbitrary File Read and Privilege Escalation via XML Binding
- CVE-2026-134284Vikunja from 1.0.0 before 2.8.0 Account Takeover via OIDC Email Fallback
- CVE-2026-123528Vikunja before 2.7.1 Insufficient Session Expiration via HTTP Token Middleware
- CVE-2026-134265Vikunja 2.4.0 before 2.8.0 Denial of Service via Unbounded Table Rowspan/Colspan
- CVE-2026-134268Vikunja 0.21.0 before 2.8.0 Denial of Service via Project Position Recalculation
No corrections so far. Something wrong on this page? Report an error.