Résumé
Snipe-IT has missing object-level authorization in Kits API
Détails de l’avis
Impact
The API endpoint for adding a license to a predefined kit (POST /api/v1/kits/{kit_id}/licenses) only checks whether the caller can edit kits, but does not perform object-level authorization on the referenced license itself. Because of this, a low-privilege user with only predefined-kit permissions can still bind a license that they should not be allowed to access or manage into a kit.
Références
- https://github.com/advisories/GHSA-crv3-j83j-f3r6
- https://github.com/grokability/snipe-it/security/advisories/GHSA-crv3-j83j-f3r6
- https://nvd.nist.gov/vuln/detail/CVE-2026-55478
- https://github.com/grokability/snipe-it/commit/0d870d540d27107634f3134e0e7f106b3faa6992
- https://github.com/grokability/snipe-it/releases/tag/v8.6.2
Vulnérabilités liées
Tout Supply chain →- MEDIUMCVE-2026-107850
Contao: Improper access control in the preview links module
- MEDIUMCVE-2026-91980
Vikunja: Any user can enumerate every team and its members by attaching arbitrary teams to a throwaway project
- MEDIUMCVE-2026-91984
Vikunja: Cross-tenant task-position rows can be injected into arbitrary project views via the unvalidated project_view_id in the task position endpoint (v1 and v2)
- HIGHCVE-2026-91985
Vikunja: Read-only project members can obtain any link share's access hash via the single-share read endpoint (v1 and v2) and escalate to the share's permission level
- HIGHCVE-2026-76216
Vikunja: Link-share principal-type confusion enables cross-account team removal, bot takeover, and roster disclosure
- CRITICALCVE-2026-68582
Vikunja: Link-share token reads any tenant's kanban buckets and enumerates usernames/IDs instance-wide (BOLA)