Vikunja before 2.7.1 Sensitive Token Exposure via URL Query in Access Logs
Affects Vikunja versions before 2.7.1 on the default single-binary deployment, where HTTP request logging is on by default. Fixed in 2.7.1.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.7.1
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Default single-binary Vikunja deployment HTTP request logging enabled, which is on by default
- Published
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 16/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Vikunja, the open-source task manager, before version 2.7.1 places live password-reset, email-confirmation, and account-deletion tokens in the URL of emailed links, so anyone who can read Vikunja's access logs or a reverse proxy's logs can capture them. An attacker who reaches those logs over the network, which requires high privileges and user interaction, could replay an unused password-reset token to take over an account or an account-deletion token to confirm a deletion.
Read the original description
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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.4/10CVSS 8.4
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Default single-binary Vikunja deployment HTTP request logging enabled, which is on by defaultUpgrade to a fixed version: 2.7.1.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- go-vikunja vikunja
fixed in 2.7.1
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123512
Is CVE-2026-123512 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Clicking a password-reset or account-deletion link writes the live token into the HTTP access logs. Anyone who can read those logs could use an unredeemed token to set a new password or confirm an account deletion.Source: github.com
Which versions are affected by CVE-2026-123512?
vikunja: before 2.7.1.Source: cve.now feed data
Am I affected, and how do I check?
Vikunja versions before 2.7.1 are in range, with the default single-binary deployment and HTTP request logging enabled, which is on by default and writes to stdout at Info level. Check the installed Vikunja version and whether HTTP request logging is turned on in the configuration.Source: github.com
How do I fix CVE-2026-123512?
Upgrade to Vikunja 2.7.1 or later, which fixes the issue.Source: github.com