CVE-2026-33675: CWE-918: Server-Side Request Forgery (SSRF) in go-vikunja vikunja
Vikunja is an open-source self-hosted task management platform. Prior to version 2.2.1, the migration helper functions `DownloadFile` and `DownloadFileWithHeaders` in `pkg/modules/migration/helpers.go` make arbitrary HTTP GET requests without any SSRF protection. When a user triggers a Todoist or Trello migration, file attachment URLs from the third-party API response are passed directly to these functions, allowing an attacker to force the Vikunja server to fetch internal network resources and return the response as a downloadable task attachment. Version 2.2.1 patches the issue.
AI Analysis
Technical Summary
CVE-2026-33675 is a Server-Side Request Forgery (SSRF) vulnerability identified in the open-source self-hosted task management platform Vikunja, specifically in versions prior to 2.2.1. The root cause lies in the migration helper functions DownloadFile and DownloadFileWithHeaders located in pkg/modules/migration/helpers.go, which perform HTTP GET requests without any validation or SSRF protections. During migrations from third-party services like Todoist or Trello, file attachment URLs obtained from their API responses are passed directly to these functions. This design flaw allows an attacker to supply crafted URLs that cause the Vikunja server to make arbitrary HTTP requests to internal network resources or other unintended destinations. The server then returns the fetched content as downloadable task attachments, potentially leaking sensitive internal information or enabling further attacks within the internal network. The vulnerability requires low privileges (PR:L) but no user interaction (UI:N), and it affects confidentiality (partial data disclosure) and availability (potentially causing resource exhaustion or denial of service). The vulnerability has a CVSS 3.1 base score of 6.4, categorized as medium severity. No known exploits have been reported in the wild as of the publication date. The issue is resolved in Vikunja version 2.2.1, which implements proper SSRF protections and input validation to prevent arbitrary HTTP requests. The vulnerability is tracked under CWE-918 (Server-Side Request Forgery).
Potential Impact
The SSRF vulnerability in Vikunja can have significant impacts on organizations running vulnerable versions, especially those self-hosting the platform in environments with sensitive internal networks. Attackers can exploit this flaw to make the Vikunja server perform unauthorized HTTP requests to internal services that are otherwise inaccessible externally. This can lead to unauthorized disclosure of sensitive internal data, such as configuration files, metadata, or internal APIs. Additionally, attackers might leverage SSRF to interact with internal services to escalate privileges, pivot within the network, or cause denial of service by exhausting server resources. Since the vulnerability affects confidentiality and availability, organizations risk data leakage and service disruption. The requirement of low privileges means that any authenticated user with migration capabilities can potentially exploit this, increasing the attack surface. Although no exploits are currently known in the wild, the presence of this vulnerability in a popular open-source platform used globally means that attackers may develop exploits, increasing risk over time. Organizations with critical internal infrastructure accessible from the Vikunja server are particularly at risk.
Mitigation Recommendations
To mitigate CVE-2026-33675, organizations should immediately upgrade Vikunja to version 2.2.1 or later, where the vulnerability is patched with proper SSRF protections and input validation. Until upgrading is possible, administrators should restrict the Vikunja server's outbound network access using firewall rules or network segmentation to prevent it from reaching sensitive internal resources. Implement strict allowlists for outbound HTTP requests originating from the Vikunja server, limiting them to trusted external domains only. Review and restrict user permissions to ensure only trusted users can perform migrations involving external URLs. Monitor logs for unusual migration activity or unexpected outbound HTTP requests. Additionally, consider deploying web application firewalls (WAFs) with SSRF detection capabilities to detect and block suspicious requests. Regularly audit and update all dependencies and monitor for new vulnerabilities in the Vikunja platform. Finally, educate users about the risks of importing data from untrusted sources during migrations.
Affected Countries
United States, Germany, United Kingdom, France, Canada, Australia, Netherlands, Sweden, Japan, South Korea
CVE-2026-33675: CWE-918: Server-Side Request Forgery (SSRF) in go-vikunja vikunja
Description
Vikunja is an open-source self-hosted task management platform. Prior to version 2.2.1, the migration helper functions `DownloadFile` and `DownloadFileWithHeaders` in `pkg/modules/migration/helpers.go` make arbitrary HTTP GET requests without any SSRF protection. When a user triggers a Todoist or Trello migration, file attachment URLs from the third-party API response are passed directly to these functions, allowing an attacker to force the Vikunja server to fetch internal network resources and return the response as a downloadable task attachment. Version 2.2.1 patches the issue.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-33675 is a Server-Side Request Forgery (SSRF) vulnerability identified in the open-source self-hosted task management platform Vikunja, specifically in versions prior to 2.2.1. The root cause lies in the migration helper functions DownloadFile and DownloadFileWithHeaders located in pkg/modules/migration/helpers.go, which perform HTTP GET requests without any validation or SSRF protections. During migrations from third-party services like Todoist or Trello, file attachment URLs obtained from their API responses are passed directly to these functions. This design flaw allows an attacker to supply crafted URLs that cause the Vikunja server to make arbitrary HTTP requests to internal network resources or other unintended destinations. The server then returns the fetched content as downloadable task attachments, potentially leaking sensitive internal information or enabling further attacks within the internal network. The vulnerability requires low privileges (PR:L) but no user interaction (UI:N), and it affects confidentiality (partial data disclosure) and availability (potentially causing resource exhaustion or denial of service). The vulnerability has a CVSS 3.1 base score of 6.4, categorized as medium severity. No known exploits have been reported in the wild as of the publication date. The issue is resolved in Vikunja version 2.2.1, which implements proper SSRF protections and input validation to prevent arbitrary HTTP requests. The vulnerability is tracked under CWE-918 (Server-Side Request Forgery).
Potential Impact
The SSRF vulnerability in Vikunja can have significant impacts on organizations running vulnerable versions, especially those self-hosting the platform in environments with sensitive internal networks. Attackers can exploit this flaw to make the Vikunja server perform unauthorized HTTP requests to internal services that are otherwise inaccessible externally. This can lead to unauthorized disclosure of sensitive internal data, such as configuration files, metadata, or internal APIs. Additionally, attackers might leverage SSRF to interact with internal services to escalate privileges, pivot within the network, or cause denial of service by exhausting server resources. Since the vulnerability affects confidentiality and availability, organizations risk data leakage and service disruption. The requirement of low privileges means that any authenticated user with migration capabilities can potentially exploit this, increasing the attack surface. Although no exploits are currently known in the wild, the presence of this vulnerability in a popular open-source platform used globally means that attackers may develop exploits, increasing risk over time. Organizations with critical internal infrastructure accessible from the Vikunja server are particularly at risk.
Mitigation Recommendations
To mitigate CVE-2026-33675, organizations should immediately upgrade Vikunja to version 2.2.1 or later, where the vulnerability is patched with proper SSRF protections and input validation. Until upgrading is possible, administrators should restrict the Vikunja server's outbound network access using firewall rules or network segmentation to prevent it from reaching sensitive internal resources. Implement strict allowlists for outbound HTTP requests originating from the Vikunja server, limiting them to trusted external domains only. Review and restrict user permissions to ensure only trusted users can perform migrations involving external URLs. Monitor logs for unusual migration activity or unexpected outbound HTTP requests. Additionally, consider deploying web application firewalls (WAFs) with SSRF detection capabilities to detect and block suspicious requests. Regularly audit and update all dependencies and monitor for new vulnerabilities in the Vikunja platform. Finally, educate users about the risks of importing data from untrusted sources during migrations.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-23T16:34:59.930Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69c2b1b2f4197a8e3b48d1be
Added to database: 3/24/2026, 3:45:54 PM
Last enriched: 3/24/2026, 4:05:25 PM
Last updated: 5/7/2026, 4:33:44 AM
Views: 46
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.