Skip to main content
VulnerabilityPublished

CVE-2026-123507: vikunja · NULL Pointer Dereference

Affects vikunjaSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.1 Medium : upgrade to 2.7.1 when convenient.

Data as of 8 Nov 2026, 02:19 UTC

CVSS 4.0 base score
5.1Medium
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.1
CNA (VulnCheck)CVSS 3.12.7
Patch
Available – fixed in 2.7.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 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 7 Nov 2026.

What to do

Upgrade vikunja to 2.7.1.

Affected software

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

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

AI-suggested

Upgrade to Vikunja version 2.7.1 or later, where this vulnerability is fixed. No other mitigation or workaround is indicated.

Description

Vikunja versions from 0.24.0 up to but not including 2.7.1 contain a nil pointer dereference vulnerability. This flaw allows project administrators to cause project views to break by saving a filter-mode bucket configuration with a null filter. The validation function skips nil entries, leading to a panic and HTTP 500 errors for all project members when the view is accessed. The issue is fixed in version 2.7.1.

References

Community reviews

Loading reviews…