Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-68582Published 2026-08-02

CVE-2026-68582 — go-vikunja vikunja

medium

As of 2026-08-03, CVE-2026-68582 is a MEDIUM-severity vulnerability in go-vikunja vikunja, CVSS v3.1 6.5, EPSS 0.2% (11.4th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-68582 as of 2026-08-03; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v3.1
6.5/10Medium
EPSS
0.2%Higher than 11.4% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
3.7/10Threadlinqs triage score
Published
Updated 2026-08-03
CVSS v3.1 6.5 (MEDIUM) · CVSS v4.0 9.3 · EPSS 0.2% (higher than 11.4% of all scored CVEs) · Priority 3.7/10 · Published 2026-08-02

Last updated:

What is CVE-2026-68582?

Vikunja versions >= 0.24.0 and <= 2.3.0 contain a broken object level authorization (BOLA) vulnerability in the task-collection endpoint (GET /api/v1/projects/{project}/views/{view}/tasks). The endpoint loads the requested project view from the URL path without verifying the caller is authorized for it. For a link-share token holder, the task scope is pinned to the share's own project, but the view is taken from the attacker-controlled path and never re-validated. As a result, a holder of any project share link can read any other tenant's kanban bucket records — bucket titles and the full created_by user object (username, name, id) — for every view in the instance. The same missing pre-authorization view load also creates a project/view-ID existence oracle (404 vs. non-404) usable by link shares and ordinary authenticated users. Task contents remain constrained to the share's own project and are not disclosed. Fixed in 2.4.0.

The record classifies CVE-2026-68582 under weakness class CWE-639. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs low-privilege credentials, needs no user interaction, and has high impact on confidentiality. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 109 days ago.

Severity and exploitation probability

CVSS v3.1 base score
6.5 — MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CVSS v4.0 base score
9.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
EPSS (FIRST)
0.2% probability of exploitation in the next 30 days, higher than 11.4% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
3.7/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-08-02

Is CVE-2026-68582 being exploited?

It currently carries a trending score of 32 in the Threadlinqs vulnerability feed.

Affected products and versions

  • go-vikunja: vikunja

How to fix CVE-2026-68582

Vendor advisory: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-rj9j-8772-4h6c. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

Threat activity tracking CVE-2026-68582

No threat campaign in the Threadlinqs corpus currently references CVE-2026-68582, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org, NVD, FIRST EPSS. This product uses the NVD API but is not endorsed or certified by the NVD.

Vendor advisory and patch

Third-party advisory