go-vikunja up to 2.2.x iCalendar VTODO Entry crlf injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.13 |
Summary
A vulnerability described as problematic has been identified in go-vikunja vikunja up to 2.2.x. Affected is an unknown function of the component iCalendar VTODO Entry Handler. Executing a manipulation can lead to crlf injection. This vulnerability is tracked as CVE-2026-35601. The attack can be launched remotely. No exploit exists. Upgrading the affected component is recommended.
Details
A vulnerability has been found in go-vikunja vikunja up to 2.2.x and classified as problematic. This vulnerability affects an unknown code block of the component iCalendar VTODO Entry Handler. The manipulation with an unknown input leads to a crlf injection vulnerability. The CWE definition for the vulnerability is CWE-93. The product uses CRLF (carriage return line feeds) as a special element, e.g. to separate lines or records, but it does not neutralize or incorrectly neutralizes CRLF sequences from inputs. As an impact it is known to affect integrity. CVE summarizes:
Vikunja is an open-source self-hosted task management platform. Prior to 2.3.0, the CalDAV output generator builds iCalendar VTODO entries via raw string concatenation without applying RFC 5545 TEXT value escaping. User-controlled task titles containing CRLF characters break the iCalendar property boundary, allowing injection of arbitrary iCalendar properties such as ATTACH, VALARM, or ORGANIZER. This vulnerability is fixed in 2.3.0.
The advisory is shared for download at github.com. This vulnerability was named CVE-2026-35601 since 04/03/2026. The exploitation appears to be easy. The attack can be initiated remotely. There are neither technical details nor an exploit publicly available.
Upgrading to version 2.3.0 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.2VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 4.1
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Crlf injectionCWE: CWE-93 / CWE-74 / CWE-707
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: vikunja 2.3.0
Patch: github.com
Timeline
04/03/2026 CVE reserved04/10/2026 Advisory disclosed
04/10/2026 VulDB entry created
04/10/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-2g7h-7rqr-9p4r
Status: Confirmed
CVE: CVE-2026-35601 (🔒)
GCVE (CVE): GCVE-0-2026-35601
GCVE (VulDB): GCVE-100-356872
Entry
Created: 04/10/2026 20:20Changes: 04/10/2026 20:20 (67)
Complete: 🔍
Cache ID: 216:9E3:103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.