CVE-2026-68581Network attack vectorHinoki check available

Cross-account API token issuance via principal ID collision

Published Aug 2, 2026 · Updated Aug 2, 2026

Incorrect authorization in Vikunja 0.22.0 through 2.3.0 allows remote authenticated users to issue target-owned API tokens. The /api/v1/tokens handlers pass a generic web.Auth.GetID() value into user-owned token queries and writes without verifying a regular-user principal. An ordinary account with a writable project and a reachable link-share ID collision can read token metadata, mint scoped credentials under the target's permissions, and delete target-owned tokens.

CVSS severity8.1
High
EPSS probability0.42%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Incorrect authorization in Vikunja 0.22.0 through 2.3.0 allows remote authenticated users to issue target-owned API tokens. The /api/v1/tokens handlers pass a generic web.Auth.GetID() value into user-owned token queries and writes without verifying a regular-user principal. An ordinary account with a writable project and a reachable link-share ID collision can read token metadata, mint scoped credentials under the target's permissions, and delete target-owned tokens.

The record

CVE
CVE-2026-68581
Published
Aug 2, 2026
Updated
Aug 2, 2026
Vendor
Vikunja
Product
Vikunja
Classifications
CWE-863, CWE-639, T1550.001
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 2, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 2, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0.22.0 <2.4.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Vikunja · Vikunjaversion=0.22.0 <2.4.0

Published CVSS scores

8.6VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
8.1GitHubCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-863Incorrect Authorization
CWE-639Authorization Bypass Through User-Controlled Key
T1550.001Application Access Token

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo