Read the docs

Incorrect authorization in Vikunja exposes private task data via webhooks

Priority LOW 30CWE-863Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
Passive
Attack complexity
Low
Attack requirements
None
Impact type
Security bypass
Confidentiality · integrity · availability
High · None · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-863.

Summary

Vikunja from 0.23.0 before 2.7.1 contains an incorrect authorization flaw (CWE-863) that lets project collaborators with write access read tasks from projects they cannot access. By registering webhooks, an attacker receives related_tasks titles, descriptions and metadata from private projects whenever another user modifies a linked task. Webhook payloads are built with the triggering user's permissions, not the webhook owner's, which exposes this data.

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

Description from the CNA

Vikunja from 0.23.0 before 2.7.1 contains an information disclosure vulnerability that allows project collaborators with write access to read tasks from inaccessible projects by registering webhooks. Because webhook payloads are built with the triggering user's permissions, attackers receive related_tasks titles, descriptions and metadata from private projects whenever another user modifies a linked task.

Why it matters now

EPSS 0.00312 24th percentileScored 2026-11-08
Fix Fixed vikunja (go-vikunja): 2.7.1

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
go-vikunjavikunja0.23.0 to before 2.7.12.7.1Patch availableCNA
  • vikunja Vendorgo-vikunja Affected 0.23.0 to 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

Upgrade Vikunja to version 2.7.1.

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 LOW 39 LOW

    Other records, highest priority first

    • TI-2026-86673 Pagination limit bypass in Vikunja lets users exhaust resourcesPriority LOW 38
    • TI-2026-86654 Vikunja exposes password-reset tokens in access logsPriority LOW 36
    • TI-2026-86670 Insufficient session expiration in Vikunja token middlewarePriority LOW 33

Timeline

  1. 2026-11-08 Threatist record created from CVE-2026-123524
  2. 2026-11-08 Alias added: GHSA-h94h-5hrj-rqqg
  3. 2026-11-09 Priority changed: MEDIUM → LOW

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