Skip to main content
CVE-2026-134281VulnerabilityPublished

Vikunja from 2.2.0 before 2.8.0 contains an information disclosure vulnerability that allows authenticated users to

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-134281· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium : upgrade to 2.8.0 when convenient.

Data as of 21 Nov 2026, 19:58 UTC

CVSS 4.0 base score
5.3Medium
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.05.3
CNA (VulnCheck)CVSS 3.14.3
Patch
Available – fixed in 2.8.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/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 21 Nov 2026.

What to do

Upgrade vikunja to 2.8.0.

Affected software

ProductAffectedFixed in
go-vikunjavikunjaAffected
  • >=2.2.0 <2.8.0
Fixed in
  • 2.8.0
Govikunjapkg:golang/vikunjaOther threatsAffected
  • >=2.2.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

If you cannot patch yet, restrict webhook registrations to trusted users and monitor webhook configurations to limit exposure.

Description

Vikunja versions from 2.2.0 up to but not including 2.8.0 have an information disclosure vulnerability. Authenticated users can exploit the tasks.overdue webhook to read private project details of other users, including project titles, descriptions, and owner IDs. This occurs by registering a personal tasks.overdue webhook with a subscribed overdue task and receiving sensitive data at external URLs.

References

Community reviews

Loading reviews…