Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-68582 – Broken Object Level Authorization (Cross-Tenant Data Disclosure) – Vikunja 0.24.0 t

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-68582 is a Broken Object Level Authorization (BOLA) vulnerability in Vikunja (go-vikunja), the open-source task and project management application. A holder of any link-share token can read kanban view data belonging to projects outside their authorized scope, resulting in cross-tenant metadata and user-information disclosure. It affects Vikunja versions 0.24.0 through 2.3.0 and is rated Critical.

Technical details

  • Root cause: The TaskCollection.ReadAll handler loads a kanban view directly from URL parameters without confirming the caller is authorized for that view. For link-share tokens, the query is pinned to the share’s project, but the requested view is not re-validated against that same project scope (CWE-639, Authorization Bypass Through User-Controlled Key).
  • Trigger conditions: An attacker in possession of any valid project link-share token requests foreign views, e.g. GET /api/v1/projects/{projectID}/views/{viewID}/tasks, substituting project and view IDs they do not own.
  • Attack vector: Network. Exploitation requires only a link-share token; no account authentication or user interaction is needed.
  • Impact: Unauthorized read access to kanban bucket records across tenant boundaries, disclosing bucket titles and creator user objects (usernames, names, and user IDs). Sequential ID testing (200 vs. 404 responses) yields a project/view existence oracle enabling instance-wide enumeration. Task contents within other projects remain protected.

Affected software

  • Vikunja (go-vikunja) versions >= 0.24.0 and <= 2.3.0

Severity

  • CVSS v4.0 base score: 9.3 (Critical) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H
  • CVSS v3.1 base score: 6.5 (Medium) — CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: Upgrade to Vikunja 2.4.0, which enforces that link-share tokens can only resolve views belonging to their authorized project.
  • If no patch: Restrict or revoke project link-share tokens, and limit network exposure of the Vikunja API to trusted clients until the upgrade can be applied.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: Vikunja, … | Vikunja

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge