All vulnerabilities
CVE-2026-91971GHSA-4vh2-39rq-rq8jGO-2026-6717

code.vikunja.io/api: Vikunja: Unbounded image decode on avatar and project-background uploads enables decode/resize amplification

go-vikunja code.vikunja.io/apigoLibraries & packages
CVSS
7.1High
ExploitationPublic exploit codeCISA's assessment says proof of concept code is public, assessed 21 Sep 2026. Not in the KEV catalogCISA via CVE List
Exploit odds (EPSS)0.44%Chance of exploitation activity in the next 30 days, higher than 36% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed in2.6.0Fixed versionGitHub
Published15 Sep 2026Updated 19 Oct 2026CVE List

What fixes it

  • 2.6.0code.vikunja.io/api, goGitHubgo get code.vikunja.io/api@v2.6.0
  • 2.6.0vikunjaCVE List
  • 2.6.0code.vikunja.io/api, GoOSVgo get code.vikunja.io/api@v2.6.0

A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.

Description

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/task_attachment.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)

PUT /api/v1/user/settings/avatar/upload   avatar=8000x8000 PNG (64MP, 192KB) -> 200 (accepted; exceeds the 50MP attachment cap)
PUT /api/v1/user/settings/avatar/upload   avatar=20000x10 PNG (681 bytes)    -> 200 after ~19.6s of server processing

Contrast (guard present): uploading the 64MP PNG as a task attachment and requesting its preview returns in ~1ms without decoding — GetPreview rejects it via maxPixels and falls back to the raw file.

Impact

A small crafted upload drives disproportionate CPU and memory on the avatar and background paths. Repeated or concurrent requests can exhaust server resources. Amplification comes from both the missing input pixel cap and the height-fixed resize, so an input-side cap alone is insufficient.

Fix

Apply a pixel-dimension cap (as on the attachment path) to the avatar and background decode paths, and bound the resize output dimensions (cap width as well as height).

Text from GitHub Advisory Database

Affected versions 4

  • code.vikunja.io/api, go<= 2.5.0GitHub
  • vikunjaaffected: all versions before 2.6.0CVE List
  • vikunjaunaffected: 2.6.0CVE List
  • code.vikunja.io/api, Gofrom first release, fixed in 2.6.0OSV

References 6