Skip to main content
Menu
CVEs

Go Vikunja API trello API token exposure in migration logs

Affects Vikunja 0.16.0 through 2.7.1 when a Trello migration fails with a transport error. CVSS rates it Low. Fixed in 2.8.0.

CVE-2026-134277Published November 21, 2026, updated

2.1LowCNA
Exploited
No known exploitation
Fix
Fixed in 2.8.0
Who is exposed
Specific setups only

Summary

Written by a model

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.

What to do

  1. Check whether your setup matches what the bug needs.

    Vikunja versions >= 0.16.0 and <= 2.7.1 (affected range before 2.8.0). A Trello migration must fail with a transport error (e.g. api.trello.com unreachable). Sentry error telemetry is enabled, or logs are readable, for the token to be exposed there.
  2. Upgrade to a fixed version: 2.8.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-134277 (Vikunja 0.16.0 before 2.8.0 Trello API Token Exposure via Migration Logs), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-134277 (entry last updated 2026-11-21):
Affected:
- Go package code.vikunja.io/api: from 0.16.0, fixed in 2.8.0
Fixed versions: 2.8.0.
Conditions (all must be true for the bug to be hit):
- Vikunja versions >= 0.16.0 and <= 2.7.1 (affected range before 2.8.0). (source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-rwwc-w83j-9f95)
- A Trello migration must fail with a transport error (e.g. api.trello.com unreachable). (source: https://www.vulncheck.com/advisories/vikunja-0.16.0-before-2.8.0-trello-api-token-exposure-via-migration-logs)
- Sentry error telemetry is enabled, or logs are readable, for the token to be exposed there. (source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-rwwc-w83j-9f95)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-134277 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134277 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-rwwc-w83j-9f95
- https://www.vulncheck.com/advisories/vikunja-0.16.0-before-2.8.0-trello-api-token-exposure-via-migration-logs
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-134277
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134277"}.

Affected versions

cve.now Index

20Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Affects Go packages
  • Severity2.1/10CVSS 2.1
  • No patch0/5No signal

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active
  • Would score about 27 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · go-vikunja/vikunja · Advisory GHSA-rwwc-w83j-9f95
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134277
RecordNVD · CVE-2026-134277
Other links 1
Linkvulncheck.com · advisories/vikunja-0.16.0-before-2.8.0-trello-api-token-exposure-via-migration-logs

Questions about CVE-2026-134277

Is CVE-2026-134277 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?

When a Trello migration fails with a transport error, the URL error embeds the user's reusable Trello API token. That token is written to application logs and, when enabled, to Sentry, so anyone with access to those logs or telemetry can read it.

Source: github.com, vulncheck.com

Which versions are affected by CVE-2026-134277?

code.vikunja.io/api (Go): from 0.16.0 before 2.8.0.

Source: cve.now feed data

Am I affected, and how do I check?

Vikunja versions 0.16.0 through 2.7.1 are in the affected range. Exposure also requires a Trello migration that fails with a transport error, such as api.trello.com being unreachable, and either Sentry error telemetry enabled or readable application logs.

Source: github.com, vulncheck.com

How do I fix CVE-2026-134277?

Upgrade to Vikunja 2.8.0, the first version outside the affected range.

Source: github.com, vulncheck.com

No corrections so far. Something wrong on this page? Report an error.