CVE-2026-54329: Snipe/snipe it Snipe-IT API Vulnerable To Cross-Tenant Vulnerability
HIGHCVE-2026-54329 is a HIGH (CVSS 8.5) snipe-it api vulnerable to cross-tenant vulnerability (CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) affecting Snipe/snipe it libraries in the Packagist ecosystem. The issue involves snipe-it api vulnerable to cross-tenant accessory injection. Remediation is available by upgrading affected packages to version 8.6.2.
CVE-2026-54329 at a Glance
Security Impact
CVSS: 8.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:L).
How to Fix CVE-2026-54329
To remediate this vulnerability, upgrade all affected Snipe/snipe it dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade snipe/snipe-it to 8.6.2
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for snipe/snipe-it
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-54329, inspect your project dependencies for Snipe/snipe it:
inspect dependencies for snipe/snipe-it
Analyze the terminal output to locate any version of Snipe/snipe it in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 8.6.2), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection'), where the product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. In Snipe/snipe it, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-54329 Affected Snipe/snipe it Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
snipe/snipe-it
|
Packagist |
< 8.6.2
|
8.6.2
|
References
Frequently Asked Questions
What is CVE-2026-54329?
Which Snipe/snipe it versions are affected?
What version fixes CVE-2026-54329?
Is snipe/snipe-it affected?
What is the CVSS score of CVE-2026-54329?
What CWE is associated with CVE-2026-54329?
How can I check Packagist dependencies for CVE-2026-54329?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-pwpj-p52h-q484",
"modified" : "2026-06-23T23:12:04Z",
"published" : "2026-06-23T23:12:04Z",
"aliases" : [ "CVE-2026-54329" ],
"summary" : "Snipe-IT API Vulnerable to Cross-Tenant Accessory Injection",
"details" : "### Impact\nA 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.\n\nThe 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.\n\nAs 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.\n\n### Patches\nPatched in https://github.com/grokability/snipe-it/commit/dc8cbf4786bb38b260b4ae1723ec9e7f81d82fe5",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:L"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Packagist",
"name" : "snipe/snipe-it"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "8.6.2"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 8.6.1"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/grokability/snipe-it/security/advisories/GHSA-pwpj-p52h-q484"
}, {
"type" : "WEB",
"url" : "https://github.com/grokability/snipe-it/commit/dc8cbf4786bb38b260b4ae1723ec9e7f81d82fe5"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/grokability/snipe-it"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-74" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-06-23T23:12:04Z",
"nvd_published_at" : null
}
}