How severe is GHSA-f95f-77jx-fcjc?

No CVSS score has been assigned to GHSA-f95f-77jx-fcjc yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-f95f-77jx-fcjc?

GHSA-f95f-77jx-fcjc affects the following packages: code.vikunja.io/api (Go). Ecosystems affected: Go.

How do I fix GHSA-f95f-77jx-fcjc?

Update code.vikunja.io/api to 2.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f95f-77jx-fcjc is resolved across your whole dependency graph.

How do I detect GHSA-f95f-77jx-fcjc in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for code.vikunja.io/api. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-f95f-77jx-fcjc if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-f95f-77jx-fcjc?

O3 pinpoints whether GHSA-f95f-77jx-fcjc is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-f95f-77jx-fcjc actively exploited in the wild?

No public exploit code has been indexed for GHSA-f95f-77jx-fcjc yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-f95f-77jx-fcjc?

GHSA-f95f-77jx-fcjc is classified as CWE-639 (CWE-639). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-f95f-77jx-fcjc published, and has it been updated?

GHSA-f95f-77jx-fcjc was published on March 25, 2026 and was last updated on March 26, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-f95f-77jx-fcjc

GHSA-f95f-77jx-fcjc is a CWE-639 vulnerability in code.vikunja.io/api. O3 Security confirms whether GHSA-f95f-77jx-fcjc is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Vikunja has a Link Share Delete IDOR — Missing Project Ownership Check Allows Cross-Project Link Share Deletion

Also known asCVE-2026-33700GO-2026-4850

Published

Mar 25, 2026

Updated

Mar 26, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🐹code.vikunja.io/api

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Summary

The DELETE /api/v1/projects/:project/shares/:share endpoint does not verify that the link share belongs to the project specified in the URL. An attacker with admin access to any project can delete link shares from other projects by providing their own project ID combined with the target share ID.

Details

The permission check in canDoLinkShare (pkg/models/link_sharing_permissions.go:53-70) validates admin access on the project from the :project URL parameter. However, the Delete method at pkg/models/link_sharing.go:305 queries only WHERE id = ? using the share ID, without verifying it belongs to the URL-specified project:

func (share *LinkSharing) Delete(s *xorm.Session, _ web.Auth) (err error) {
    _, err = s.Where("id = ?", share.ID).Delete(share)
    return
}

This is the same vulnerability class as GHSA-jfmm-mjcp-8wq2 (task attachment IDOR) and the fixed GHSA-mr3j-p26x-72x4 (task comment IDOR).

Additionally, ReadOne at line 203 has the same pattern (WHERE id = ? only), though it is not currently exploitable because CanRead fails first due to an unrelated issue with the hash parameter binding.

Impact

An authenticated user with admin access to any project can:

Delete link shares belonging to any other project in the system
Disrupt collaboration by removing shared access links
Link share IDs are sequential integers, making enumeration trivial

Reproduction

User A creates Project A and a link share on it (share ID = X)
User B creates Project B (gaining admin access)
User B calls DELETE /api/v1/projects/{projectB_id}/shares/{X}
The permission check passes (User B is admin on Project B)
The delete executes WHERE id = X — deleting User A's link share

Recommended Fix

Change Delete at pkg/models/link_sharing.go:305 to:

_, err = s.Where("id = ? AND project_id = ?", share.ID, share.ProjectID).Delete(share)

Also fix ReadOne at line 203 as defense in depth.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`code.vikunja.io/api`	all versions	2.2.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for code.vikunja.io/api. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update code.vikunja.io/api to 2.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f95f-77jx-fcjc is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-f95f-77jx-fcjc is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-f95f-77jx-fcjc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary The `DELETE /api/v1/projects/:project/shares/:share` endpoint does not verify that the link share belongs to the project specified in the URL. An attacker with admin access to any project can delete link shares from other projects by providing their own project ID combined with the target share ID. ## Details The permission check in `canDoLinkShare` (`pkg/models/link_sharing_permissions.go:53-70`) validates admin access on the project from the `:project` URL parameter. However, the `Delete` method at `pkg/models/link_sharing.go:305` queries only `WHERE id = ?` using the share ID,

O3 Security · Impact-Aware SCA

Is GHSA-f95f-77jx-fcjc in your dependencies?

O3 detects GHSA-f95f-77jx-fcjc across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works