medium · CVSS v3 5.2 · CVSS v4 6.9

CVE-2026-123502

Vikunja before 2.7.1 logs raw URIs for the /shares/:share/auth route, exposing link‑share hashes in logs. Attackers with access to these log

Overview

Vikunja before 2.7.1 logs raw URIs for the /shares/:share/auth route, exposing link‑share hashes in logs. Attackers with access to these logs can reuse the hashes to obtain project JWTs with read, write, or admin permissions. This allows unauthorized access to project data and potentially to modify or delete content.

Description

Vikunja before 2.7.1 contains an information exposure vulnerability that allows log readers to obtain link-share hashes because the request logger records the raw URI of the /shares/:share/auth route. Attackers with access to Vikunja or reverse proxy access logs can reuse non-expiring, non-password-protected share hashes to obtain a project JWT with read, write or admin permission.

Impact

Confidentiality: attackers can read project data via leaked JWTs. Integrity: potential unauthorized modifications or deletions. Availability: not directly impacted. Defenders: system administrators and security teams monitoring log access and JWT usage.

Remediation

Upgrade to Vikunja 2.7.1 or later to fix the logging issue. Configure reverse proxies or logging middleware to mask or omit raw URIs for the /shares/:share/auth route. Restrict log file access to privileged users only. Rotate existing project JWTs and invalidate any leaked share hashes.

Risk context

The vulnerability has a medium severity (CVSS v3 5.2, v4 6.9) and no EPSS data. While it does not directly affect availability, it poses a moderate risk to confidentiality and integrity. Prompt patching and log hardening are recommended.

Affected products

  • Vikunja

Scores

Severity
medium
CVSS v2
6.8
CVSS v3
5.2
CVSS v4
6.9
EPSS
—

information-exposure log-leak Vikunja JWT medium-severity access-control

← All CVEs