Read the docs

Vikunja exposes password-reset tokens in access logs

Priority MEDIUM 52CWE-532Published · Updated

Key facts

Attack vector
Network
Privileges required
High
User interaction
Passive
Attack complexity
Low
Attack requirements
None
Impact type
Information disclosure
Confidentiality · integrity · availability
High · High · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-532.

Summary

Vikunja before 2.7.1 places live password-reset, email-confirmation and account-deletion tokens in the URL query string of emailed links. When a user clicks such a link, the full request URI is written to Vikunja's HTTP access log and to any reverse-proxy logs (CWE-532). An attacker with high privileges who can read those logs can replay an unredeemed password-reset token to take over an account, or an account-deletion token to confirm the deletion.

Written with Claude Haiku 5.5 from the sources below · 2026-11-08

Description from the CNA

Vikunja before 2.7.1 embeds live password-reset, email-confirmation and account-deletion tokens in the URL query string of emailed links, so the full request URI, including the token, is written to Vikunja's HTTP access log and any reverse-proxy logs when a user clicks the link. Attackers with read access to those logs can replay an unredeemed password-reset token to take over the account or an account-deletion token to confirm the deletion.

Why it matters now

Fix Fixed vikunja (go-vikunja): 2.7.1

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
go-vikunjavikunjabefore 2.7.12.7.1Patch availableCNA
  • vikunja Vendorgo-vikunja Affected before 2.7.1 Fixed in 2.7.1 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:vikunja:vikunja:*:*:*:*:*:*:*:*——go-vikunja
  • cpe:2.3:a:vikunja:vikunja:*:*:*:*:*:*:*:* Versions — — ·go-vikunja

Remediation

Update Vikunja to version 2.7.1, the fixed version. The sources list no advisory identifier for this fix.

Written with Claude Haiku 5.5 from the sources below · 2026-11-08

  • Fix · CNA vikunja (go-vikunja) Fixed in 2.7.1

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    go-vikunja vikunja 2.7.1

    39 records Highest priority Priority MEDIUM 20 MEDIUM, 19 LOW

    Other records, highest priority first

    • TI-2026-86673 Pagination limit bypass in Vikunja lets users exhaust resourcesPriority MEDIUM 53
    • TI-2026-86670 Insufficient session expiration in Vikunja token middlewarePriority MEDIUM 48
    • TI-2026-86655 Credential exposure in Vikunja lets attackers steal auth tokensPriority MEDIUM 48

Timeline

  1. 2026-11-08 Threatist record created from CVE-2026-123512
  2. 2026-11-08 Alias added: GHSA-x6wm-4pvf-x539

References

  • TI-2026-40929 Authorization bypass in go-vikunja Vikunja CVSS 4.0CRITICAL 9.3
  • TI-2026-21967 Vijkunja has Weak Password Policy Combined with Persistent Sessions After Password Change CVSS 3.1CRITICAL 9.1
  • TI-2026-62115 Vikunja before 2.6.0 Privilege Escalation via Link Share Hash CVSS 4.0HIGH 8.7
  • TI-2026-62108 Vikunja before 2.6.0 Authentication Bypass via CalDAV BasicAuth CVSS 4.0HIGH 8.7
  • TI-2026-62107 Vikunja before 2.6.0 Authentication Bypass via Unthrottled API CVSS 4.0HIGH 8.7
  • TI-2026-26971 Vikunja ahs a TOTP Two-Factor Authentication Bypass via OIDC Login Path CVSS 3.1CRITICAL 9.1
See all 105 →

Sources