Is CVE-2026-123517 exploited in the wild?

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

How severe is CVE-2026-123517?

Medium severity, with a CVSS score of 4.3, published 8 November 2026.

Which products and versions are affected?

Go-Vikunja Vikunja before 2.7.1.

Is there a fix for CVE-2026-123517?

Yes: fixed in 2.7.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-123517 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-123517?

Check whether you run Go-Vikunja 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-123517: Vikunja information disclosure in team self-removal endpoint

CVE-2026-123517 · Severity: medium · CVSS 4.3 · Published 2026-11-08

Vikunja is a task and project management platform. Authenticated users can probe the system to discover whether private teams exist and learn limited details about them—such as whether a team is SSO-managed or has only one member—without needing access to those teams. While no team names or member information leak, this enumeration capability could enable reconnaissance attacks.

Vendors: Go-Vikunja.

Quick answers

Is CVE-2026-123517 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-123517 being exploited in the wild.
How severe is CVE-2026-123517?: Medium severity, with a CVSS score of 4.3, published 8 November 2026.
Which products and versions are affected?: Go-Vikunja Vikunja before 2.7.1.
Is there a fix for CVE-2026-123517?: Yes: fixed in 2.7.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-123517 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-123517?: Check whether you run Go-Vikunja 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

Fixed in: 2.7.1

Technical details

The vulnerability exists in the TeamMember.CanDelete authorization check, which returns true for self-removal requests without verifying the caller is actually a team member. An attacker can send DELETE requests to /teams/{id}/members/{own username} for arbitrary team IDs and use the distinguishable HTTP responses (404, 412, specific error messages, or 200) to infer whether a team exists, is externally managed, or has a single member. The attack requires authentication but no team membership.

Affected products

go-vikunja Vikunja before 2.7.1

Timeline

2026-10-22: disclosed
2026-11-08: advisory

References

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