Token scope bypass in Vikunja lets attackers manage user webhooks
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- Low · Low · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-863.
Summary
Vikunja from 2.2.0 before 2.7.1 contains an authorization bypass in which holders of tokens scoped only to projects_webhooks can manage the owner's user-level webhooks by supplying user_id in request bodies. An attacker with such a token can register user webhooks pointing to their own receiver to obtain reminders and task payloads from all owner projects, and can read, change or delete existing user webhooks. The flaw is classified as CWE-863 Incorrect Authorization.
Written with Claude Haiku 5.5 from the sources below · 2026-11-08
Description from the CNA
Vikunja from 2.2.0 before 2.7.1 contains an authorization bypass vulnerability that allows holders of tokens scoped only to projects_webhooks to manage the owner's user-level webhooks by supplying user_id in request bodies. Attackers can register user webhooks to their own receiver to obtain reminders and task payloads from all owner projects, and read, change or delete existing user webhooks.
Why it matters now
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
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| go-vikunja | vikunja | 2.2.0 to before 2.7.1 | 2.7.1 | Patch available | CNA |
- vikunja Vendorgo-vikunja Affected 2.2.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.
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:vikunja:vikunja:*:*:*:*:*:*:*:* | — | — | go-vikunja |
- cpe:2.3:a:vikunja:vikunja:*:*:*:*:*:*:*:* Versions — — ·go-vikunja
Remediation
The sources list a fixed version for vikunja: upgrade go-vikunja vikunja to 2.7.1 or later.
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
- 2026-11-08 Threatist record created from CVE-2026-123506
- 2026-11-08 Alias added: GHSA-2fc5-hwxx-39f7
- 2026-11-09 CISA SSVC decision points changed
References
More go-vikunja vulnerabilities
- 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
Sources
- CVE-2026-123506 · CVE Program
- CVE-2026-123506 · NVD
- FIRST EPSS
- GHSA-2fc5-hwxx-39f7 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences