Is CVE-2026-54329 exploited in the wild?

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

How severe is CVE-2026-54329?

High severity, with a CVSS score of 8.5, 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-54329?

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-54329 attacked?

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

Am I affected by CVE-2026-54329?

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-54329: Grokability Snipe-IT mass assignment in Accessories API

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

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-54329 attacked?

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

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

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-54329 · Severity: high · CVSS 8.5 · Published 2026-07-10

Snipe-IT is an open-source IT asset management system used by organizations to track hardware, software licenses, and accessories. A security flaw in the system's API allows a user belonging to one company to create records for a different company when the 'Full Multiple Companies Support' feature is enabled. This could lead to unauthorized data entry and organizational confusion in multi-tenant environments.

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

Quick answers

Is CVE-2026-54329 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-54329 being exploited in the wild.
How severe is CVE-2026-54329?: High severity, with a CVSS score of 8.5, 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-54329?: 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-54329 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-54329?: 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

A mass assignment vulnerability exists in the Snipe-IT Accessories API prior to version 8.6.2. The 'store' method in the Accessories API controller uses the 'fill()' method with all request parameters, and because the 'company_id' field was mass-assignable, it allowed users to bypass intended multi-tenant boundaries. When 'Full Multiple Companies Support' (FMCS) is enabled, a low-privileged authenticated user can provide a 'company_id' in their API request to create accessory records associated with a different company. The fix involves explicitly setting the 'company_id' using a server-side check of the current user's authorized company scope. This issue is addressed in version 8.6.2.

Affected products

Grokability Snipe-IT < 8.6.2

Identifiers

CVE-2026-54329
GHSA-pwpj-p52h-q484

Timeline

2026-07-10: disclosed
2026-07-10: advisory
2026-07-10: patched: Fixed in version 8.6.2

References

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