CVE-2026-55478

Snipe-IT: Missing object-level authorization in Kits API

Published Jul 10, 2026 CVSS 4.0 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
Snipe-IT is an IT asset/license management system. Prior to 8.6.2, POST /api/v1/kits/{kit_id}/licenses checks whether the caller can edit kits but does not authorize access to the referenced license object, allowing a low-privilege user with predefined-kit permissions to bind a license they should not be able to access or manage into a kit. This issue is fixed in version 8.6.2.

Analysis

AI-generated

Technical impact

Snipe‑IT’s Kits API fails to perform a required object‑level authorization check. When an authenticated user sends a POST request to /api/v1/kits/{kit_id}/licenses, the system verifies that the caller has permission to edit the kit but does not verify that the caller can access the referenced license. Consequently, a user with only kit‑editing privileges can bind a license they would normally be barred from accessing or managing. The flaw is catalogued as CWE‑639.

Affected Systems

All installations of grokability:snipe‑it earlier than version 8.6.2 are affected. The issue was resolved in release 8.6.2 and remains fixed in all subsequent versions.

Risk and Exploitability

The likely attack vector is a network‑based API call that an authenticated user can execute from the web interface or an API client; this inference comes from the description’s mention of a POST request. Exploitation requires only kit‑edit permissions and no higher privilege. The CVSS score of 5.3 denotes moderate severity, while the EPSS score, being below 1%, indicates a low probability of exploitation. The vulnerability is not listed in the CISA KEV catalog. Although the exploitation likelihood is low, the impact on environments where kit‑edit rights are granted means that mitigation is essential.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the vendor release v8.6.2 or later which includes the authorization fix
  • Restrict kit‑edit permissions to users who also have permission to access the relevant licenses
  • Audit existing kit‑license associations for unauthorized bindings and correct any that were created before the patch

Generated by OpenCVE AI on August 3, 2026 at 03:59 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-crv3-j83j-f3r6 Snipe-IT has missing object-level authorization in Kits API
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Grokability
Grokability snipe-it
Vendors & Products Grokability
Grokability snipe-it
Type Values Removed Values Added
Description Snipe-IT is an IT asset/license management system. Prior to 8.6.2, POST /api/v1/kits/{kit_id}/licenses checks whether the caller can edit kits but does not authorize access to the referenced license object, allowing a low-privilege user with predefined-kit permissions to bind a license they should not be able to access or manage into a kit. This issue is fixed in version 8.6.2.
Title Snipe-IT: Missing object-level authorization in Kits API
Weaknesses CWE-639
References
Metrics cvssV4_0

{'score': 5.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jul 10, 2026, 8:58 PM
Reserved
Jun 16, 2026, 10:28 PM
Status
Analyzed
Published
Jul 10, 2026, 7:17 PM
Modified
Oct 25, 2026, 3:10 PM