Is CVE-2026-55482 exploited in the wild?

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

How severe is CVE-2026-55482?

Medium severity, with a CVSS score of 6.3, published 19 August 2026.

Which products and versions are affected?

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

Is there a fix for CVE-2026-55482?

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

How is CVE-2026-55482 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-55482?

Check whether you run snipe/snipe-it (Packagist) or Snipeitapp Snipe-It 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-55482: Grokability Snipe-IT multi-tenancy bypass in Bulk Asset Update

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

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

Q: How is CVE-2026-55482 attacked?

It is attacked over the network, in a network appliance.

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

Check whether you run snipe/snipe-it (Packagist) or Snipeitapp Snipe-It 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-55482 · Severity: medium · CVSS 6.3 · Published 2026-08-19

Snipe-IT, an open-source IT asset management system, contains a flaw that allows users to bypass multi-tenancy restrictions. In environments where multiple companies share the same system, a regular user can move assets between different companies. This could lead to unauthorized access to asset records and disruption of inventory management across different business units or clients.

Technologies: snipe/snipe-it (Packagist), Snipeitapp Snipe-It. Vendors: Packagist, Snipeitapp.

Quick answers

Is CVE-2026-55482 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-55482 being exploited in the wild.
How severe is CVE-2026-55482?: Medium severity, with a CVSS score of 6.3, published 19 August 2026.
Which products and versions are affected?: snipe/snipe-it (Packagist) <= 8.4.1, ECOSYSTEM:introduced=0,fixed=8.4.2.
Is there a fix for CVE-2026-55482?: Yes. snipe/snipe-it (Packagist): upgrade to 8.4.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-55482 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-55482?: Check whether you run snipe/snipe-it (Packagist) or Snipeitapp Snipe-It 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.4.2 or later
```
composer require snipe/snipe-it:^8.4.2
```

Technical details

An authorization bypass (CWE-639) exists in the BulkAssetsController::update() method of Snipe-IT. The vulnerability stems from the application accepting a 'company_id' directly from user input without validating it against the standard company-scoping function 'Company::getIdForCurrentUser()'. An authenticated attacker with low privileges can exploit this to reassign assets to different companies, breaking the isolation intended in multi-tenant deployments. The issue is addressed in version 8.4.2 by ensuring proper company-scoping checks are applied during bulk updates.

Affected products

Grokability Snipe-IT <= 8.4.1

Identifiers

CVE-2026-55482
GHSA-33g4-646g-qwmm

Timeline

2026-06-12: disclosed: Vulnerability reported and patched in repository
2026-06-23: advisory: GitHub Advisory published

References

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