Skip to main content
VulnerabilityPublished

CVE-2026-123510: vikunja · Uncontrolled Search Path Element

Affects vikunjaSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 1.0 Low : upgrade to 2.7.1 when convenient.

Data as of 8 Nov 2026, 02:19 UTC

CVSS 4.0 base score
1.0Low
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.01.0
CNA (VulnCheck)CVSS 3.13.3
Patch
Available – fixed in 2.7.1
CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:P/VC:L/VI:L/VA:N/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
  • <2.7.1
Fixed in
  • 2.7.1
Govikunjapkg:golang/vikunjaOther threatsAffected
  • <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 go-vikunja vikunja version 2.7.1 or later, where the PluginsDir and LogPath are properly anchored to the service root path, mitigating this vulnerability. No other mitigation is indicated or required.

Description

CVE-2026-123510 is a vulnerability in go-vikunja vikunja versions before 2.7.1 where the PluginsDir and LogPath are not properly anchored to the service root path. This allows local attackers with write access to the startup working directory to plant malicious plugins or read sensitive logs, including audit logs. The issue is fixed in version 2.7.1.

References

Community reviews

Loading reviews…