CVE-2026-134277
Deferred Deferred - Pending Action

Information Disclosure in Vikunja via Trello API Token Exposure

Vulnerability report for CVE-2026-134277, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-21

Last updated on: 2026-11-21

Assigner: VulnCheck

Description

Vikunja from 0.16.0 before 2.8.0 contains an information disclosure vulnerability that writes users' Trello API tokens to application logs and Sentry by formatting provider errors verbatim in listeners.go. When a Trello migration fails with a transport error, the URL error embeds the token query parameter, letting anyone with log or telemetry access obtain the reusable third-party credential.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-21
Last Modified
2026-11-21
Generated
2026-11-21
AI Q&A
2026-11-21
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
vikunja vikunja From 0.16.0 (inc) to 2.8.0 (exc)
vikunja vikunja From 0.16.0 (inc) to 2.7.0 (inc)
vikunja vikunja From 0.16.0 (inc) to 2.7.1 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-532 The product writes sensitive information to a log file.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects Vikunja versions 0.16.0 to 2.7.0. When a Trello migration fails due to a transport error, the application logs the full error message including the Trello API token as part of the URL query parameters. This exposes the token in application logs and Sentry, allowing anyone with access to these logs to retrieve the credential.

Detection Guidance

Check Vikunja application logs and Sentry telemetry for failed Trello migration errors containing URLs with 'token' query parameters. Search logs for strings like 'Trello API token' or 'token=' in error messages.

Impact Analysis

If you use Vikunja versions between 0.16.0 and 2.7.0 and have attempted a Trello migration, your Trello API token may have been exposed in logs. Attackers with log or telemetry access could misuse this token to access your Trello account or linked services. The impact is limited by requiring access to logs but still poses a credential exposure risk.

Compliance Impact

This vulnerability could lead to non-compliance with GDPR or HIPAA due to unauthorized exposure of sensitive credentials in logs. GDPR requires protection of personal data, and HIPAA mandates safeguarding protected health information. Exposed API tokens may enable unauthorized access to third-party services, violating these regulations.

Mitigation Strategies
  • Upgrade Vikunja to version 2.8.0 or later to patch the vulnerability.
  • Review and redact any logs containing exposed Trello API tokens from past errors.
  • Rotate any Trello API tokens that may have been exposed in logs.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-134277. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...