Skip to main content
Menu
CVEs

Go Vikunja API auth bypass via TOTP replay in passcode validation

Affects Vikunja 2.2.1 through 2.7.1 on accounts with TOTP enabled. Fixed in 2.8.0.

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

6.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 2.8.0
Who is exposed
Not reported

Summary

Written by a model

Vikunja from 2.2.1 before 2.8.0 contains a TOTP replay protection bypass in ValidateTOTPPasscode that allows attackers to reuse consumed codes by padding them with whitespace. Attackers with valid credentials who observe a used passcode can resubmit it whitespace-padded to the login API within the validity window to obtain a session token.

Who should check

Teams running Vikunja 2.2.1 through 2.7.1 with TOTP two-factor login enabled, including anyone using the Go module code.vikunja.io/api.

“>= 2.2.1, <= 2.7.1”

github.com

What to do

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-134276 (Vikunja from 2.2.1 before 2.8.0 TOTP Replay Protection Bypass via Whitespace), 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-134276 (entry last updated 2026-11-21):
Affected:
- Go package code.vikunja.io/api: from 2.2.1, fixed in 2.8.0
Fixed versions: 2.8.0.
Conditions (all must be true for the bug to be hit):
- Vikunja versions 2.2.1 through 2.7.1 (fixed in 2.8.0). (source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-cxqw-2wh9-h8c9)
- TOTP is enabled on the target account. (source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-cxqw-2wh9-h8c9)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-134276 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134276 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-cxqw-2wh9-h8c9
- https://www.vulncheck.com/advisories/vikunja-from-2.2.1-before-2.8.0-totp-replay-protection-bypass-via-whitespace
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-134276
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-134276"}.

Affected versions

cve.now Index

33Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach10/20Affects Go packages
  • Severity6.3/10CVSS 6.3
  • No patch0/5No signal

What would change the score

  • Would score about 78 if added to CISA KEV
  • Would score about 73 if CISA's SSVC rates exploitation active
  • Would score about 38 if advisories confirm default setups are exposed

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-cxqw-2wh9-h8c9
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134276
RecordNVD · CVE-2026-134276
Other links 1
Linkvulncheck.com · advisories/vikunja-from-2.2.1-before-2.8.0-totp-replay-protection-bypass-via-whitespace

Questions about CVE-2026-134276

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

A TOTP code that has already been used can be submitted again if it is padded with whitespace, which gets past the replay protection. Successfully reusing the code can give a session token.

Source: github.com, vulncheck.com

Which versions are affected by CVE-2026-134276?

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

Source: cve.now feed data

Am I affected, and how do I check?

Vikunja versions 2.2.1 through 2.7.1 are affected, and only when TOTP is enabled on the account. To check, look at the Vikunja version in use and whether two-factor authentication is turned on in the account's security settings.

Source: github.com, vulncheck.com

How do I fix CVE-2026-134276?

Upgrade Vikunja to 2.8.0 or later, which fixes this issue.

Source: github.com, vulncheck.com

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