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.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.8.0
- Who is exposed
- Specific setups only
Summary
Written by a model
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.
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.
“all versions from v1.0.0 up to and including v2.7.1 are affected”
What to do
Check whether your setup matches what the bug needs.
OIDC provider has emailfallback enabled (non-default setting). Mailer is disabled, which is the default; local emails are then never verified. Local registration is enabled (default), or the attacker controls some local account. Affected Vikunja versions are 1.0.0 through 2.7.1.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-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"}.Affected versions
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach10/20Affects Go packages
- Severity7.7/10CVSS 7.7
- No patch0/5No signal
What would change the score
- Would score about 80 if added to CISA KEV
- Would score about 75 if CISA's SSVC rates exploitation active
Timeline
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · go-vikunja/vikunja · Advisory GHSA-8pm4-w983-mx58 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134284 |
| Record | NVD · CVE-2026-134284 |
| Other links 1 | |
| Link | vulncheck.com · advisories/vikunja-from-1.0.0-before-2.8.0-account-takeover-via-oidc-email-fallback |
Questions about CVE-2026-134284
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: cve.now feed data
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: github.com
Which versions are affected by CVE-2026-134284?
code.vikunja.io/api (Go): from 1.0.0 before 2.8.0.
Source: cve.now feed data
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: github.com
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: github.com
Related
- CVE-2026-123531Vikunja 1.0.0 before 2.7.1 Pagination Limit Bypass via page=0 Parameter
- CVE-2026-134282Vikunja 0.14.0 before 2.8.0 Arbitrary File Read and Privilege Escalation via XML Binding
- CVE-2026-123528Vikunja before 2.7.1 Insufficient Session Expiration via HTTP Token Middleware
- CVE-2026-134265Vikunja 2.4.0 before 2.8.0 Denial of Service via Unbounded Table Rowspan/Colspan
- CVE-2026-134266Vikunja 0.19.0 before 2.8.0 Denial of Service via Datemath Business-Day Filter
- CVE-2026-134268Vikunja 0.21.0 before 2.8.0 Denial of Service via Project Position Recalculation
No corrections so far. Something wrong on this page? Report an error.