CVE-2026-54329

Snipe-IT API Vulnerable to Cross-Tenant Accessory Injection

A cross-tenant data injection vulnerability was identified in the Snipe-IT Accessories API when Full Multiple Companies Support (FMCS) is enabled. A low-privileged authenticated user belonging to one company can create an accessory record under another company by supplying a foreign company_id value in the API request body.

The issue occurs because the API create path mass-assigns request parameters directly to the Accessory model, and the Accessory model allows company_id to be mass assigned. Unlike the web controller, which uses Company::getIdForCurrentUser() to enforce the authenticated user’s company context, the API controller does not apply equivalent tenant enforcement during accessory creation.

As a result, a Company A user can inject persistent accessory records into Company B. The injected records are then visible to Company B users as legitimate Company B inventory records. This breaks the integrity of company-scoped inventory data and represents a tenant isolation failure in the accessory creation flow.

CVE-2026-54329 has a CVSS score of 8.5 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (8.6.2); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Patched in https://github.com/grokability/snipe-it/commit/dc8cbf4786bb38b260b4ae1723ec9e7f81d82fe5

1. What is CVE-2026-54329? CVE-2026-54329 is a high-severity security vulnerability in snipe/snipe-it (composer), affecting versions <= 8.6.1. It is fixed in 8.6.2.
2. How severe is CVE-2026-54329? CVE-2026-54329 has a CVSS score of 8.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of snipe/snipe-it are affected by CVE-2026-54329? snipe/snipe-it (composer) versions <= 8.6.1 is affected.
4. Is there a fix for CVE-2026-54329? Yes. CVE-2026-54329 is fixed in 8.6.2. Upgrade to this version or later.
5. Is CVE-2026-54329 exploitable, and should I be worried? Whether CVE-2026-54329 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-54329 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-54329? Upgrade snipe/snipe-it to 8.6.2 or later.

Other vulnerabilities in snipe/snipe-it