Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-40103: CWE-836: Use of Password Hash Instead of Password for Authentication in go-vikunja vikunja

0
Medium
VulnerabilityCVE-2026-40103cvecve-2026-40103cwe-836
Published: Fri Apr 10 2026 (04/10/2026, 16:12:27 UTC)
Source: CVE Database V5
Vendor/Project: go-vikunja
Product: vikunja

Description

Vikunja is an open-source self-hosted task management platform. Prior to 2.3.0, Vikunja's scoped API token enforcement for custom project background routes is method-confused. A token with only projects.background can successfully delete a project background, while a token with only projects.background_delete is rejected. This is a scoped-token authorization bypass. This vulnerability is fixed in 2.3.0.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/11/2026, 05:19:57 UTC

Technical Analysis

CVE-2026-40103 is a scoped-token authorization bypass vulnerability in the open-source task management platform Vikunja before version 2.3.0. The issue arises because the API token enforcement for project background routes is method-confused: tokens scoped with projects.background can delete project backgrounds, whereas tokens scoped with projects.background_delete are rejected. This improper scope validation allows unauthorized deletion actions. The vulnerability is classified under CWE-836 (Use of Password Hash Instead of Password for Authentication), though the description focuses on token scope confusion. No official remediation level or patch link is provided in the data, but the issue is fixed in Vikunja 2.3.0.

Potential Impact

An attacker with a scoped API token limited to projects.background can delete project backgrounds, bypassing intended authorization restrictions. This results in unauthorized modification of project data (integrity impact) but does not affect confidentiality or availability. The CVSS 3.1 score of 4.3 reflects a medium severity impact with network attack vector, low attack complexity, and requiring privileges with no user interaction.

Mitigation Recommendations

Upgrade Vikunja to version 2.3.0 or later, where this scoped-token authorization bypass vulnerability is fixed. Since no official patch link or advisory is provided, users should verify the upgrade from the official Vikunja release notes or repository. Until upgraded, restrict API token issuance and monitor for misuse of project background tokens.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-04-09T01:41:38.536Z
Cvss Version
3.1
State
PUBLISHED
Remediation Level
null

Threat ID: 69d9d9751cc7ad14da3f8745

Added to database: 4/11/2026, 5:17:41 AM

Last enriched: 4/11/2026, 5:19:57 AM

Last updated: 4/11/2026, 3:19:27 PM

Views: 10

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses