Is CVE-2026-55478 exploited in the wild?

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

How severe is CVE-2026-55478?

Medium severity, with a CVSS score of 4, published 10 July 2026.

Which products and versions are affected?

snipe/snipe-it (Packagist) <= 8.6.1, ECOSYSTEM:introduced=0,fixed=8.6.2.

Is there a fix for CVE-2026-55478?

Yes. snipe/snipe-it (Packagist): upgrade to 8.6.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-55478 attacked?

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

Am I affected by CVE-2026-55478?

Check whether you run snipe/snipe-it (Packagist) 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-55478: grokability Snipe-IT missing object-level authorization in Kits API

Q: Is there a fix for CVE-2026-55478?

Yes. snipe/snipe-it (Packagist): upgrade to 8.6.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-55478 attacked?

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

Q: Am I affected by CVE-2026-55478?

Check whether you run snipe/snipe-it (Packagist) 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-55478 · Severity: medium · CVSS 4 · Published 2026-07-10

Snipe-IT is an open-source asset management platform that tracks hardware, software, and licenses. A flaw in its Kits API allows low-privilege users with kit management permissions to attach licenses they shouldn't have access to, bypassing license-level access controls. This could lead to unauthorized data exposure or mismanagement of restricted software licenses.

Technologies: snipe/snipe-it (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2026-55478 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-55478 being exploited in the wild.
How severe is CVE-2026-55478?: Medium severity, with a CVSS score of 4, published 10 July 2026.
Which products and versions are affected?: snipe/snipe-it (Packagist) <= 8.6.1, ECOSYSTEM:introduced=0,fixed=8.6.2.
Is there a fix for CVE-2026-55478?: Yes. snipe/snipe-it (Packagist): upgrade to 8.6.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-55478 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-55478?: Check whether you run snipe/snipe-it (Packagist) 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

snipe/snipe-it (Packagist): upgrade to 8.6.2 or later
```
composer require snipe/snipe-it:^8.6.2
```

Technical details

The POST /api/v1/kits/{kit_id}/licenses API endpoint in Snipe-IT performs authorization checks only at the kit level, verifying that the caller can edit kits, but fails to validate object-level authorization on the license being added. This is a CWE-639 authorization bypass vulnerability: an attacker with limited kit-management permissions can link any license to a kit, regardless of their permissions on that specific license. The attack vector is network-based and requires low-level authentication (kit edit privileges). No user interaction is needed. An attacker can gain unauthorized access to or modify license metadata and associations. The vulnerability affects versions 8.6.1 and earlier; patch 8.6.2 is available.

Affected products

Snipe-IT Snipe-IT <= 8.6.1

Identifiers

CVE-2026-55478
GHSA-crv3-j83j-f3r6

Timeline

2026-06-24: disclosed
2026-06-24: patched: Patch v8.6.2 released
2026-07-10: advisory: Published to NVD
2026-08-28: advisory: Published to GitHub Advisory Database

References

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