Read the docs

Insecure permissions expose Vikunja dump archives to local users

Priority LOW 29CWE-276Published · Updated

Key facts

Attack vector
Local
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
—
Confidentiality · integrity · availability
High · None · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

Vikunja before 2.7.1 by go-vikunja contains an insecure file permissions flaw (CWE-276) in the dump archive created by the vikunja dump command. Because the archive is created with umask permissions, it is world-readable, so a local user on a shared host can read it. The archive holds configuration, password hashes, TOTP secrets, tokens and stored files.

Written with Claude Haiku 5.5 from the sources below · 2026-11-08

Description from the CNA

Vikunja before 2.7.1 contains an insecure file permissions vulnerability that allows local users to read dump archives created with umask permissions by the vikunja dump command. Local attackers on a shared host can read the world-readable zip in the rootpath to obtain config, password hashes, TOTP secrets, tokens, and stored files.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00117 1st percentileScored 2026-11-16
Fix Fixed vikunja (go-vikunja): 2.7.1

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
go-vikunjavikunjabefore 2.7.12.7.1Patch availableCNA
  • vikunja Vendorgo-vikunja Affected before 2.7.1 Fixed in 2.7.1 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:vikunja:vikunja:*:*:*:*:*:*:*:*——go-vikunja
  • cpe:2.3:a:vikunja:vikunja:*:*:*:*:*:*:*:* Versions — — ·go-vikunja

Remediation

Update vikunja to version 2.7.1 or later, which fixes the flaw.

Written with Claude Haiku 5.5 from the sources below · 2026-11-08

  • Fix · CNA vikunja (go-vikunja) Fixed in 2.7.1

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    go-vikunja vikunja 2.7.1

    39 records Highest priority Priority HIGH 2 HIGH, 7 MEDIUM, 30 LOW

    Other records, highest priority first

    • TI-2026-86673 Uncontrolled resource consumption in Vikunja lets users bypass pagination limitsPriority HIGH 73
    • TI-2026-86670 Insufficient session expiration in Vikunja lets revoked tokens authenticatePriority HIGH 68
    • TI-2026-86666 Information disclosure in Vikunja webhook related_tasks payloadPriority MEDIUM 64

Timeline

  1. 2026-11-08 Threatist record created from CVE-2026-123500
  2. 2026-11-08 Alias added: GHSA-fgfv-xjh6-9vhx
  3. 2026-11-09 Priority changed: MEDIUM → LOW
  4. 2026-11-12 CISA SSVC decision points changed

References

  • TI-2026-40929 Authorization bypass in go-vikunja Vikunja CVSS 4.0CRITICAL 9.3
  • TI-2026-21967 Vijkunja has Weak Password Policy Combined with Persistent Sessions After Password Change CVSS 3.1CRITICAL 9.1
  • TI-2026-62115 Vikunja before 2.6.0 Privilege Escalation via Link Share Hash CVSS 4.0HIGH 8.7
  • TI-2026-62108 Vikunja before 2.6.0 Authentication Bypass via CalDAV BasicAuth CVSS 4.0HIGH 8.7
  • TI-2026-62107 Vikunja before 2.6.0 Authentication Bypass via Unthrottled API CVSS 4.0HIGH 8.7
  • TI-2026-26971 Vikunja ahs a TOTP Two-Factor Authentication Bypass via OIDC Login Path CVSS 3.1CRITICAL 9.1
See all 105 →

Sources