Vikjuna Bypasses Webhook SSRF Protections During OpenID Connect Avatar Download

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:L

EPSS

• CVE-2026-33679: 0.40% estimated exploitation activity in the next 30 days; percentile 34.50 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The DownloadImage function in pkg/utils/avatar.go uses a bare http.Client{} with no SSRF protection when downloading user avatar images from the OpenID Connect picture claim URL. An attacker who controls their OIDC profile picture URL can force the Vikunja server to make HTTP GET requests to arbitrary internal or cloud metadata endpoints. This bypasses the SSRF protections that are correctly applied to the webhook system. Details When a user authenticates via OpenID Connect, Vikunja extracts the picture claim from the ID token or UserInfo endpoint and passes it to syncUserAvatarFromOpenID, which calls utils.DownloadImage with the attacker-controlled URL: Claim extraction (pkg/modules/auth/openid/openid.go:70-78): Avatar sync trigger (pkg/modules/auth/openid/openid.go:348-352): Vulnerable download (pkg/utils/avatar.go:94-115): In contrast, the webhook system correctly applies SSRF protection (pkg/models/webhooks.go:306-310): The avatar download path has none of this…

Published by the source

25 Mar 2026, 21:17 UTC

Last modified by the source

30 Mar 2026, 21:13 UTC

Source last checked

26 Oct 2026, 15:19 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-g9xj-752q-xh63

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

# Patch Next advisory brief: CVE-2026-33679

Advisory: Vikjuna Bypasses Webhook SSRF Protections During OpenID Connect Avatar Download
IDs: CVE-2026-33679, GHSA-g9xj-752q-xh63
Record: https://patchnext.com/advisories/cve-2026-33679 (revision 1, source checked 26 Oct 2026, 15:19 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.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.2.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go code.vikunja.io/api: affected <= 2.2.0; fixed in 2.2.1

## 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://github.com/advisories/GHSA-g9xj-752q-xh63 (GitHub-reviewed advisory GHSA-g9xj-752q-xh63 lists affected ranges: Go code.vikunja.io/api >=0 <=2.2.0)

Commands are suggestions: review each one before running it.