Vikjuna: Link Share Hash Disclosure via ReadAll Endpoint Enables Permission Escalation

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2026-33680: 0.40% estimated exploitation activity in the next 30 days; percentile 34.85 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The LinkSharing.ReadAll() method allows link share authenticated users to list all link shares for a project, including their secret hashes. While LinkSharing.CanRead() correctly blocks link share users from reading individual shares via ReadOne, the ReadAllWeb handler bypasses this check by never calling CanRead(). An attacker with a read-only link share can retrieve hashes for write or admin link shares on the same project and authenticate with them, escalating to full admin access. Details The vulnerability arises from an inconsistency between the ReadOneWeb and ReadAllWeb generic handlers and the LinkSharing permission model. LinkSharing.CanRead() correctly blocks link share users (pkg/models/linksharingpermissions.go:25-29): ReadOneWeb calls CanRead() before returning data (pkg/web/handler/readone.go:64): ReadAllWeb does NOT call CanRead() (pkg/web/handler/readall.go:106): LinkSharing.ReadAll() only checks project-level read access (pkg/models/linksharing.go:228-236):…

Published by the source

25 Mar 2026, 21:18 UTC

Last modified by the source

30 Mar 2026, 21:14 UTC

Source last checked

26 Oct 2026, 15:19 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-8hp8-9fhr-pfm9

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-33680

Advisory: Vikjuna: Link Share Hash Disclosure via ReadAll Endpoint Enables Permission Escalation
IDs: CVE-2026-33680, GHSA-8hp8-9fhr-pfm9
Record: https://patchnext.com/advisories/cve-2026-33680 (revision 1, source checked 26 Oct 2026, 15:19 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: code.vikunja.io/api 2.2.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go code.vikunja.io/api: affected < 2.2.2; fixed in 2.2.2

## Suggested inspection (read-only)
- Go code.vikunja.io/api: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on code.vikunja.io/api.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-8hp8-9fhr-pfm9 (GitHub-reviewed advisory GHSA-8hp8-9fhr-pfm9 lists affected ranges: Go code.vikunja.io/api >=0 <2.2.2)

Commands are suggestions: review each one before running it.