Skip to main content
VulnerabilityPublished

CVE-2026-134265: vikunja · Unthrottled Resource Allocation

Affects vikunjaSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 2.8.0 soon.

Data as of 21 Nov 2026, 17:32 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.07.1
CNA (VulnCheck)CVSS 3.16.5
Patch
Available – fixed in 2.8.0
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade vikunja to 2.8.0.

Affected software

ProductAffectedFixed in
go-vikunjavikunjaAffected
  • >=2.4.0 <2.8.0
Fixed in
  • 2.8.0
Govikunjapkg:golang/vikunjaOther threatsAffected
  • >=2.4.0 <2.8.0
Fixed in
  • 2.8.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Vikunja to version 2.8.0 or later, where this vulnerability is fixed. No other mitigations or workarounds are indicated in the available data.

Description

Vikunja versions from 2.4.0 up to but not including 2.8.0 contain a denial of service vulnerability in the richtext converter. Authenticated project writers can exploit this by storing tables with unbounded rowspan and colspan values, which can exhaust server memory and CPU resources. Project readers or CalDAV clients can trigger this resource exhaustion by reading markdown tasks, performing CalDAV GET requests, or using the frontend editor, resulting in very large responses disproportionate to the original content size.

References

Community reviews

Loading reviews…