Skip to content

← Actionable
Medium, CVSS 5.4amended

Vikunja: Saved filter creation with an empty filter string recalculates task positions across all tenants

CVE-2026-111918GHSA-fprf-r6rv-xg99

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (code.vikunja.io/api 2.7.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
EPSS
  • CVE-2026-111918: 0.18% estimated exploitation activity in the next 30 days; percentile 7.18 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary In Vikunja v2.6.0 the task position recalculation that runs when a saved filter view is created fails open when the requesting user has no accessible projects. Instead of aborting, the search that feeds the recalculation loses its project scope entirely and returns every task in the instance. The server then writes one `task_positions` row per task per view (four views per filter) into views owned by the requesting user, including rows that reference tasks of other tenants the user can never see. Any authenticated user can trigger this. The impact is a cross-tenant integrity violation, a single-request write amplification primitive that scales with instance size, and a violation of the invariant stated in the fix for GHSA-w39f-h553-h2mx that position writes are scoped by project read access.

Details Vikunja computes kanban and list ordering in a shared `task_positions` table keyed by `(task_id, project_view_id)`. When a saved filter is created, `SavedFilter.Create`…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 5 · amended ·

    Amended from osv record GHSA-fprf-r6rv-xg99

  2. Revision 4 · amended ·

    Amended from ghsa record GHSA-fprf-r6rv-xg99

  3. Revision 3 · amended ·

    Amended from ghsa record GHSA-fprf-r6rv-xg99

  4. Revision 2 · amended ·

    Amended from osv record GO-2026-6731

  5. Revision 1 · created ·

    Published from osv record GHSA-fprf-r6rv-xg99

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-111918

Advisory: Vikunja: Saved filter creation with an empty filter string recalculates task positions across all tenants
IDs: CVE-2026-111918, GHSA-fprf-r6rv-xg99
Record: https://patchnext.com/advisories/cve-2026-111918 (revision 5, source checked 28 Oct 2026, 06:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: code.vikunja.io/api 2.7.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go code.vikunja.io/api: affected >= 1.0.0-rc0, < 2.7.0; fixed in 2.7.0

## Suggested inspection (read-only)
- Go code.vikunja.io/api: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on code.vikunja.io/api.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GO-2026-6731 (OSV record GO-2026-6731 lists affected ranges: Go code.vikunja.io/api >=0)
- Verified: https://osv.dev/vulnerability/GHSA-fprf-r6rv-xg99 (OSV record GHSA-fprf-r6rv-xg99 lists affected ranges: Go code.vikunja.io/api >=1.0.0-rc0 <=2.6.0)
- Verified: https://github.com/advisories/GHSA-fprf-r6rv-xg99 (GitHub-reviewed advisory GHSA-fprf-r6rv-xg99 lists affected ranges: Go code.vikunja.io/api >=1.0.0-rc0 <=2.6.0)
- Verified: https://osv.dev/vulnerability/GHSA-fprf-r6rv-xg99 (OSV record GHSA-fprf-r6rv-xg99 lists affected ranges: Go code.vikunja.io/api >=1.0.0-rc0 <2.7.0 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…