Vikunja is an open-source self-hosted task management platform. Prior to version 2.2.1, 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. Version 2.2.1 patches the issue.
CVE-2026-33679
This high-severity CVE scores 7.4 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 67% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.4
- EG Score
- 7.4(medium)
- EG Risk
- 38(Track)EG Risk 38/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity74% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 34%
- KEV
- Not listed
Published
March 24, 2026
Last Modified
June 17, 2026
Advisory Details (3)
Auto-updated Aug 2, 2026Vikunja 2.2.1 and 2.2.2: Nine security fixes, and quality of life improvements
https://vikunja.io/changelog/vikunja-v2.2.2-was-releasedSSRF via OpenID Connect Avatar Download Bypasses Webhook SSRF Protections · Advisory · go-vikunja/vikunja · GitHub
https://github.com/go-vikunja/vikunja/security/advisories/GHSA-g9xj-752q-xh63commit 363aa6642352 (go-vikunja/vikunja)
Fix landed in go-vikunja/vikunja commit 363aa6642352 — awaiting tagged release
https://github.com/go-vikunja/vikunja/commit/363aa6642352b08fc8bc6aaff2f3a550393af1cfAffected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| code.vikunja.io/api | — | 2.2.1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 29× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 19:30 UTCEPSS rescore
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 03:11 UTCEPSS rescore
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-12 15:01 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 09:37 UTCEPSS rescore
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 15:38 UTCOSV refresh
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
Show 39 moreShow fewer
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 14:17 UTCEPSS rescore
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 10:37 UTCEG score recompute
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 06:50 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 21:30 UTCEG score recompute
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-11 21:07 UTCEG score recompute
- 2026-08-11 04:09 UTCEG score recompute
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-09 17:33 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 06:27 UTCEG score recompute
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-07 16:46 UTCEG score recompute
- 2026-08-06 19:04 UTCEG score recompute
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 01:11 UTCEG score recompute
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:38 UTCEPSS rescore
- 2026-08-03 23:55 UTCEG score recompute
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 15:44 UTCEG score recompute
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-27 14:29 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
- CVE-2016-10927EG 10.0CRITICAL
- CVE-2016-10926EG 10.0CRITICAL
- CVE-2018-10511EG 10.0CRITICAL
- CVE-2018-1000124EG 10.0CRITICAL
- CVE-2017-11291EG 10.0EPSS p92CRITICAL
- CVE-2017-12905EG 10.0CRITICAL
- CVE-2017-8794EG 10.0CRITICAL
- CVE-2017-13667EG 9.9CRITICAL
- CVE-2017-17674EG 9.8CRITICAL
- CVE-2013-4864EG 9.8EPSS p93CRITICAL
Frequently asked(5)
What is CVE-2026-33679?
When was CVE-2026-33679 disclosed?
Is CVE-2026-33679 actively exploited?
What is the CVSS score of CVE-2026-33679?
How do I remediate CVE-2026-33679?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-33679
Is Your Infrastructure Affected by CVE-2026-33679?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.