Summary
Snipe-IT vulnerable to cross-company asset maintenance re-parenting via API update
Affected endpoint
PATCH /api/v1/maintenances/{maintenance_id}
Also likely affected:
PUT /api/v1/maintenances/{maintenance_id}
Preconditions
The attacker needs:
- A valid authenticated API token.
- Permission to update asset maintenance records.
- Access to a maintenance record currently attached to an asset in their own company.
The attacker does not need access to the target asset’s company.
Root cause
In the API maintenance update flow, the application checks access to the current maintenance record / current asset, then accepts attacker-controlled fields including asset_id.
The vulnerable behavior is that the new asset_id is not checked against the current user’s company scope before being saved.
Relevant code path:
app/Http/Controllers/Api/MaintenancesController.php
The update method loads the maintenance, checks access to the existing $maintenance->asset, then calls:
$maintenance->fill($request->all());
$maintenance->save();
Since asset_id is fillable on the maintenance model, the attacker can re-parent the record to another company’s asset.
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
Security impact
This breaks tenant/company isolation in multi-company deployments. A scoped user can write maintenance records against assets outside their authorized company boundary.
Potential impact includes:
- Cross-company asset history pollution.
- Unauthorized modification of another company’s asset maintenance timeline.
- Incorrect maintenance, cost, audit, and warranty records on victim-company assets.
- Loss of integrity in asset lifecycle records.
This is not intended functionality because the application’s company-scoping model should prevent users from writing records onto inaccessible assets.
Impact
The API endpoint for updating asset maintenance records allows an authorized user to change the asset_id of an existing maintenance record to an asset outside their company scope.
In a Full Multiple Company Support / multi-company deployment, this allows a user from Company A to attach or move a maintenance record onto an asset belonging to Company B. The endpoint appears to authorize access to the existing maintenance record’s asset, but does not re-authorize the newly supplied asset_id before saving the update.
CVE-2026-55516 has a CVSS score of 7.7 (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.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-55516? CVE-2026-55516 is a high-severity security vulnerability in snipe/snipe-it (composer), affecting versions <= 8.6.1. It is fixed in 8.6.2.
- How severe is CVE-2026-55516? CVE-2026-55516 has a CVSS score of 7.7 (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.
- Which versions of snipe/snipe-it are affected by CVE-2026-55516? snipe/snipe-it (composer) versions <= 8.6.1 is affected.
- Is there a fix for CVE-2026-55516? Yes. CVE-2026-55516 is fixed in 8.6.2. Upgrade to this version or later.
- Is CVE-2026-55516 exploitable, and should I be worried? Whether CVE-2026-55516 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
- What actually determines whether CVE-2026-55516 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.
- How do I fix CVE-2026-55516? Upgrade
snipe/snipe-itto 8.6.2 or later.