Read the docs

Incorrect authorization in Vikunja link share deletion

Priority MEDIUM 57CWE-863Published · Updated

Key facts

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

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

Summary

Vikunja from 0.13.0 before 2.7.0 contains an incorrect authorization flaw (CWE-863) that lets project members with Write permission delete admin-tier link shares. The delete permission check reads an unloaded share object, so the check does not work as intended. An attacker with Write permission can send DELETE requests to the v1 or v2 project shares endpoints using sequential share IDs to revoke admin links and invalidate existing share sessions.

Written with Claude Haiku 5.5 from the sources below · 2026-10-28

Description from the CNA

Vikunja 0.13.0 before 2.7.0 contains an incorrect authorization vulnerability that allows project members with Write permission to delete admin-tier link shares because the delete permission check reads an unloaded share object. Attackers can send DELETE requests to the v1 or v2 projects shares endpoints with sequential share IDs to revoke admin links and invalidate existing share sessions.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00213 11th percentileScored 2026-11-07
Fix Fixed vikunja (go-vikunja): 2.7.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
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-vikunjavikunja0.13.0 to before 2.7.02.7.0Patch availableCNA
  • vikunja Vendorgo-vikunja Affected 0.13.0 to before 2.7.0 Fixed in 2.7.0 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.0 or later, which fixes the flaw.

Written with Claude Haiku 5.5 from the sources below · 2026-10-28

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

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.0

    5 records Highest priority Priority HIGH 1 HIGH, 3 MEDIUM, 1 LOW

    Other records, highest priority first

    • TI-2026-76128 Permissive CORS policy trusting localhost origins in VikunjaPriority HIGH 67
    • TI-2026-76125 Improper access revocation in Vikunja webhooks exposes project dataPriority MEDIUM 64
    • TI-2026-76123 Vikunja WebSocket Authentication Ignores Session RevocationPriority MEDIUM 64

Timeline

  1. 2026-10-18 Threatist record created from CVE-2026-111921
  2. 2026-10-18 Alias added: GHSA-92qc-qm37-9wr9
  3. 2026-10-21 CISA SSVC decision points changed
  4. 2026-10-21 Priority changed: LOW → MEDIUM

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