Is CVE-2026-56765 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-56765 being exploited in the wild.

How severe is CVE-2026-56765?

Critical severity, with a CVSS score of 9.8, published 10 July 2026.

Which products and versions are affected?

code.vikunja.io/api (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=2.2.1; Vikunja < 2.2.1.

Is there a fix for CVE-2026-56765?

Yes. code.vikunja.io/api (Go): upgrade to 2.2.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-56765 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-56765?

Check whether you run code.vikunja.io/api (Go) or Vikunja at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-56765: Vikunja authorization bypass and IDOR in LinkSharing and TaskAttachments

Q: Is there a fix for CVE-2026-56765?

Yes. code.vikunja.io/api (Go): upgrade to 2.2.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-56765 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-56765?

Check whether you run code.vikunja.io/api (Go) or Vikunja at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-56765 · Severity: critical · CVSS 9.8 · Published 2026-07-10

Vikunja, an open-source collaboration and task management platform, contains security flaws that allow unauthorized users to access and delete files across an entire organization. By using a single publicly shared link, an attacker can escalate their permissions to gain administrative control over project shares. This allows them to download or permanently delete every file attachment from every project on the server, leading to significant data theft and operational disruption.

Technologies: code.vikunja.io/api (Go), Vikunja. Vendors: Go, Vikunja.

Quick answers

Is CVE-2026-56765 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-56765 being exploited in the wild.
How severe is CVE-2026-56765?: Critical severity, with a CVSS score of 9.8, published 10 July 2026.
Which products and versions are affected?: code.vikunja.io/api (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=2.2.1; Vikunja < 2.2.1.
Is there a fix for CVE-2026-56765?: Yes. code.vikunja.io/api (Go): upgrade to 2.2.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-56765 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-56765?: Check whether you run code.vikunja.io/api (Go) or Vikunja at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

code.vikunja.io/api (Go): upgrade to 2.2.1 or later
```
go get code.vikunja.io/api@v2.2.1
```

Technical details

Vikunja contains two critical authorization flaws. First, the 'LinkSharing.ReadAll' endpoint fails to redact share hashes when returning project shares to users with read-only access, allowing an attacker to obtain admin-level share hashes and escalate privileges. Second, the 'GetTaskAttachment' endpoint (ReadOne) suffers from an Insecure Direct Object Reference (IDOR) vulnerability; while it validates permissions against a provided task ID, it retrieves the actual attachment using a sequential ID without verifying that the attachment belongs to the authorized task. By chaining these, a remote attacker with access to a single public link share can enumerate, download, and delete all file attachments across all projects on the instance. The vulnerabilities are patched in version 2.2.1.

Affected products

Vikunja Vikunja < 2.2.1

Identifiers

CVE-2026-56765
GHSA-2pv8-4c52-mf8j
GO-2026-4855

Timeline

2026-03-23: advisory: Initial GHSA advisory published
2026-07-10: disclosed: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.