Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-68581Published 2026-08-02

CVE-2026-68581 — go-vikunja vikunja

high

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

CVSS v3.1
8.1/10High
EPSS
0.3%Higher than 24.6% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
5/10Threadlinqs triage score
Published
Updated 2026-08-03
CVSS v3.1 8.1 (HIGH) · CVSS v4.0 8.6 · EPSS 0.3% (higher than 24.6% of all scored CVEs) · Priority 5/10 · Published 2026-08-02

Last updated:

What is CVE-2026-68581?

Vikunja versions 0.22.0 through 2.3.0 fail to validate the principal type in API token management. Because user IDs and link-share IDs are independent numeric sequences and both resolve through a generic web.Auth.GetID() interface, a link-share JWT whose numeric ID equals a target user's ID is treated as that user by the /api/v1/tokens endpoints. An authenticated attacker can obtain a target's numeric user ID via authenticated user search, then create link shares on an attacker-writable project until the link-share sequence reaches that value, and use the resulting link-share JWT to list, create, and delete the target user's API tokens (including issuing a new token with attacker-chosen scopes under the target's permissions). Fixed in version 2.4.0.

The record classifies CVE-2026-68581 under weakness class CWE-863. 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, integrity. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 64 days ago.

Severity and exploitation probability

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

Is CVE-2026-68581 being exploited?

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

Affected products and versions

  • go-vikunja: vikunja

How to fix CVE-2026-68581

No vendor patch reference has been recorded for CVE-2026-68581 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

Threat activity tracking CVE-2026-68581

No threat campaign in the Threadlinqs corpus currently references CVE-2026-68581, 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, GitHub Security Advisories. Last verified by Threadlinqs on . This product uses the NVD API but is not endorsed or certified by the NVD.

Vendor advisory and patch

Third-party advisory