Vulnerability in code.vikunja.io/api (CVE-2026-56765)
Summary
Vulnerability in code.vikunja.io/api (CVE-2026-56765). Confidential information can be exposed externally. Exploitable via GET /api/v1/projects/. Mitigation: upgrade to 2.2.1 or later.
Original description
The description as published by the source.
Vikunja before 2.2.1 contains an authorization flaw where the LinkSharing.ReadAll endpoint exposes share hashes to users with read access, enabling permission escalation to admin-level shares. The GetTaskAttachment endpoint performs permission checks against user-supplied task IDs but fetches attachments by sequential ID without verifying ownership, allowing attackers to download and delete all file attachments across all projects instance-wide.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-56765 has been found in code.vikunja.io/api.
Attackers can target a specific entry point like GET /api/v1/projects/ over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 9.8/10.
What to do: upgrade code.vikunja.io/api to 2.2.1 or later.
If unsure, ask your IT team or search "code.vikunja.io/api CVE-2026-56765" on the vendor's site.
CVE-2026-56765 (code.vikunja.io/api) — CWE-639 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /api/v1/projects/ / POST /shares/{hash}/auth / GET /projects/{id}/shares / POST /shares/{admin_hash}/auth
Patched: 2.2.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-639) exists in code.vikunja.io/api. Attackers reach the vulnerable code path via GET /api/v1/projects/ without authentication.
Check the vendor advisory for the affected versions of code.vikunja.io/api. Attack surface: GET /api/v1/projects/ / POST /shares/{hash}/auth / GET /projects/{id}/shares / POST /shares/{admin_hash}/auth.
Severity: Critical (CVSS 9.8/10). Confidential information can be exposed externally.
Update to 2.2.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /api/v1/projects/ requests with malformed payloads or SQL meta-characters. Run grep -r 'code.vikunja.io/api' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'code.vikunja.io/api' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
code.vikunja.io/apiを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /api/v1/projects/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/v1/projects/への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade code.vikunja.io/api to 2.2.1ステージング環境で 2.2.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /api/v1/projects/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory vulncheck.com
- advisory github.com
- package github.com
- web github.com
- web github.com
- web github.com
- web vikunja.io