Vikunja: Unbounded image decode on avatar and project-background uploads enables decode/resize amplification
CVE-2026-91971GHSA-4vh2-39rq-rq8j
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (code.vikunja.io/api 2.6.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
- Affected
- <= 2.5.0
- Fixed in
- 2.6.0
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GO-2026-6717 lists affected ranges: Go code.vikunja.io/api >=0
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-4vh2-39rq-rq8j lists affected ranges: Go code.vikunja.io/api >=0 <2.6.0 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-4vh2-39rq-rq8j lists affected ranges: Go code.vikunja.io/api >=0 <=2.5.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 7.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source
- EPSS
- CVE-2026-91971: 0.44% estimated exploitation activity in the next 30 days; percentile 37.90 (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 The 50-megapixel decode guard exists only on the task-attachment preview path. Avatar and project-background uploads decode uploaded images with no pixel cap. Worse, the avatar resize fixes the output height at 1024 and derives the width from the aspect ratio, so a tiny extreme-aspect-ratio PNG expands to an enormous output image — an input-side pixel cap would not catch it. Details The only maxPixels check (50MP) is in TaskAttachment.GetPreview (pkg/models/taskattachment.go ~lines 332-338). No such check guards: - avatar upload: pkg/modules/avatar/upload/upload.go (~lines 82, 137, 141) - project background: pkg/modules/background/handler/background.go (~lines 174, 269, 289) imaging.Resize(img, 0, 1024, imaging.Lanczos) (upload.go ~line 141) fixes height=1024 and derives width from the aspect ratio: a 20000x10 input yields a ~2,048,000 x 1024 output (~2.1 billion pixels), so a few-hundred-byte file drives huge CPU and memory. PoC (verified at runtime against v2.5.0) Contrast…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 4 · amended ·
Amended from ghsa record GHSA-4vh2-39rq-rq8j
- Revision 3 · amended ·
Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.
- Revision 2 · amended ·
Amended from osv record GO-2026-6717
- Revision 1 · created ·
Published from osv record GHSA-4vh2-39rq-rq8j
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-91971 Advisory: Vikunja: Unbounded image decode on avatar and project-background uploads enables decode/resize amplification IDs: CVE-2026-91971, GHSA-4vh2-39rq-rq8j Record: https://patchnext.com/advisories/cve-2026-91971 (revision 4, source checked 26 Oct 2026, 15:32 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.1) 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.6.0. A vendor fix does not mean a deployment is fixed. ## Affected components - Go code.vikunja.io/api: affected <= 2.5.0; fixed in 2.6.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-6717 (OSV record GO-2026-6717 lists affected ranges: Go code.vikunja.io/api >=0) - Verified: https://osv.dev/vulnerability/GHSA-4vh2-39rq-rq8j (OSV record GHSA-4vh2-39rq-rq8j lists affected ranges: Go code.vikunja.io/api >=0 <2.6.0 (fixed)) - Verified: https://github.com/advisories/GHSA-4vh2-39rq-rq8j (GitHub-reviewed advisory GHSA-4vh2-39rq-rq8j lists affected ranges: Go code.vikunja.io/api >=0 <=2.5.0) Commands are suggestions: review each one before running it.
Loading voting…