# CVE-2026-29794: Vikunja has Rate-Limit Bypass for Unauthenticated Users via Spoofed Headers

> Attackers can bypass rate limits by spoofing IP headers, enabling unlimited requests for brute-force attacks against unauthenticated endpoints.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Mar 2026
- **Updated:** 20 Mar 2026
- **Also known as:** GHSA-m547-hp4w-j6jx, GO-2026-4791

## What is CVE-2026-29794?

CVE-2026-29794 is a medium-severity vulnerability in go-vikunja vikunja, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vikunja is an open-source self-hosted task management platform. Starting in version 0.8 and prior to version 2.2.0, unauthenticated users are able to bypass the application's built-in rate-limits by spoofing the `X-Forwarded-For` or `X-Real-IP` headers due to the rate-limit relying on the value of `(echo.Context).RealIP`. Unauthenticated users can abuse endpoints available to them for different potential impacts. The immediate concern would be brute-forcing usernames or specific accounts' passwords. This bypass allows unlimited requests against unauthenticated endpoints. Version 2.2.0 patches the issue.

Weakness: CWE-807 (Reliance on Untrusted Inputs in a Security Decision)

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

3 open source packages ship an affected version, including code.vikunja.io/api. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `code.vikunja.io/api` | Go | All versions | None |
| `code.vikunja.io/api` | Go | From 0.8 | 2.2.0 |
| `code.vikunja.io/api` | Go | From 0.8 | 2.2.0 |

Products: Vikunja Vikunja.

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

Upgrade code.vikunja.io/api to 2.2.0 or later.

## Is CVE-2026-29794 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-29794 exists.

## Other vulnerabilities in go-vikunja vikunja

- [CVE-2026-28268](https://insights.sbomify.com/CVE-2026-28268/): Vikunja Vulnerable to Account Takeover via Password Reset Token Reuse (critical 9.8)
- [CVE-2026-27575](https://insights.sbomify.com/CVE-2026-27575/): Vijkunja has Weak Password Policy Combined with Persistent Sessions After Password Change (critical 9.1)
- [CVE-2026-25935](https://insights.sbomify.com/CVE-2026-25935/): Vikunja Affected by XSS Via Task Preview (high 8.6)
- [CVE-2026-35595](https://insights.sbomify.com/CVE-2026-35595/): Vikunja Affected by Privilege Escalation via Project Reparenting (high 8.3)
- [CVE-2026-33316](https://insights.sbomify.com/CVE-2026-33316/): Vikunja’s Improper Access Control Enables Bypass of Administrator-Imposed Account Disablement (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-29794 and fix it if it is affected.

What it is: CVE-2026-29794 is a medium-severity vulnerability in go-vikunja vikunja, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-29794 exists.

Affected packages and fixed versions:
- code.vikunja.io/api (Go): affected all versions; no fix listed
- code.vikunja.io/api (Go): affected from 0.8; fixed in 2.2.0
- code.vikunja.io/api (Go): affected from 0.8; fixed in 2.2.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-29794/ (Markdown: https://insights.sbomify.com/CVE-2026-29794/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-29794
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-29794
- OSV: https://osv.dev/vulnerability/CVE-2026-29794

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-29794/
Summaries are generated and may contain mistakes; the official description above is the record.