CVE-2026-123527

Description

Vikunja from 2.4.0 before 2.7.1 contains an authorization bypass vulnerability that allows token holders to perform unintended operations due to colliding v1 and v2 API token permission keys. Attackers with a token scoped to read project backgrounds can delete them via the v2 DELETE background route, and bucket create-only tokens can update existing buckets.

Severity
MEDIUM
CVSS v3
5.4
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L · source cna
CVSS v4
5.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N · source cna
Exploit chance (EPSS)
0.238%
chance of exploitation in the next 30 days
higher than 14.9% of scored CVEs · 2026-11-18
CISA KEV
Not listed
Public exploit code
None public
Exploit references (NVD and CNA): 0
Metasploit modules: 0
Nuclei templates: 0

Weakness

CISA SSVC decision points

Exploitationpoc
Automatableno
Technical impactpartial
Scored2026-11-12

Timeline

  1. 2026-11-08Published by the CNA01:37 UTC
  2. 2026-11-12CISA SSVC decision recorded4 days after publication

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
go-vikunja vikunjafrom 2.4.0 before 2.7.1fixed in 2.7.12.7.1
vikunja vikunjafrom 2.4.0 before 2.7.1fixed in 2.7.12.7.1

Products and versions as NVD and the vendor that published the CVE list them.

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources