Skip to main content
CVE-2026-123528VulnerabilityPublished

Vikunja before 2.7.1 contains an insufficient session expiration vulnerability that allows holders of revoked access

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-123528· High 7.6

Not known to be exploited · CVSS 7.6 High : upgrade to 2.7.1 soon.

Data as of 8 Nov 2026, 06:49 UTC

CVSS 4.0 base score
7.6High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.07.6
CNA (VulnCheck)CVSS 3.16.8
Patch
Available – fixed in 2.7.1
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.

What to do

Upgrade vikunja to 2.7.1.

Affected software

ProductAffectedFixed in
go-vikunjavikunjaAffected
  • <2.7.1
Fixed in
  • 2.7.1
Govikunjapkg:golang/vikunjaOther threatsAffected
  • <2.7.1
Fixed in
  • 2.7.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Vikunja version 2.7.1 and later. Users should upgrade to version 2.7.1 or newer to address this vulnerability. Since no vendor advisory or patch links are provided, confirm patch availability from official Vikunja sources before deployment.

Description

Vikunja versions prior to 2.7.1 have a vulnerability in session expiration handling. This flaw allows users holding revoked access tokens to continue authenticating because the SetupTokenMiddleware bypasses session and account-status verification. Consequently, attackers with stolen tokens can maintain persistent access by minting OAuth sessions or API tokens even after logout, password reset, or account disabling.

References

Community reviews

Loading reviews…