Skip to main content

Over 150 LLM Providers · Over 5,300 Models The most extensible AI-powered pentesting platform. Open source. Star on GitHub

CVE-2026-35595

8.3 · HIGH
Published Apr 10, 2026 vikunja CWE-269

Overview

CVE-2026-35595 is a high-severity vulnerability affecting vikunja vikunja. It was published on April 10, 2026 and has a CVSS 3.1 base score of 8.3 (HIGH).

This vulnerability has a CVSS 3.1 base score of 8.3, rated HIGH. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

Technical Description

Vikunja is an open-source self-hosted task management platform. Prior to 2.3.0, the CanUpdate check at pkg/models/project_permissions.go:139-148 only requires CanWrite on the new parent project when changing parent_project_id. However, Vikunja's permission model uses a recursive CTE that walks up the project hierarchy to compute permissions. Moving a project under a different parent changes the permission inheritance chain. When a user has inherited Write access (from a parent project share) and reparents the child project under their own project tree, the CTE resolves their ownership of the new parent as Admin (permission level 2) on the moved project. This vulnerability is fixed in 2.3.0.

Remediation

Check the references section for vendor advisories and patches from vikunja. Update vikunja to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected Products

Vendor Product Versions Status
vikunja vikunja >= 0, < 2.3.0 Affected

Frequently Asked Questions

What is CVE-2026-35595?

CVE-2026-35595 is a high-severity vulnerability affecting vikunja vikunja. It was published on April 10, 2026 and has a CVSS 3.1 base score of 8.3 (HIGH).

How severe is CVE-2026-35595?

This vulnerability has a CVSS 3.1 base score of 8.3, rated HIGH. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-35595?

Check the references section for vendor advisories and patches from vikunja. Update vikunja to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-35595?

CyberStrike's AI-powered security agents can automatically detect CVE-2026-35595 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.