# CVE-2026-55516: Snipe-IT: Cross-company asset maintenance re-parenting via API update

> An authorized user can move maintenance records to assets outside their company scope via API, bypassing authorization checks.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-575r-357h-fhch

## What is CVE-2026-55516?

CVE-2026-55516 is a high-severity missing authorization vulnerability in Snipeitapp Snipe-It, published on 10 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Snipe-IT is an IT asset/license management system. Prior to 8.6.2, PATCH or PUT /api/v1/maintenances/{maintenance_id} checks access to the current maintenance record and asset but then fills attacker-controlled fields including asset_id without re-authorizing the newly supplied asset, allowing an authorized user to move a maintenance record onto an asset outside their company scope. This issue is fixed in version 8.6.2.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-55516?

2 open source packages ship an affected version, including snipe/snipe-it. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `snipe/snipe-it` | Packagist | All versions | 8.6.2 |
| `snipe/snipe-it` | Packagist | All versions | 8.6.2 |

Products: Snipeitapp Snipe-It.

## How do I fix CVE-2026-55516?

Upgrade snipe/snipe-it to 8.6.2 or later.

## Is CVE-2026-55516 being exploited?

There is no known exploitation of CVE-2026-55516 in the wild and no public exploit code.

## Other vulnerabilities in Snipeitapp Snipe-It

- [CVE-2025-63601](https://insights.sbomify.com/CVE-2025-63601/): File upload in n/a (critical 9.9)
- [CVE-2026-37709](https://insights.sbomify.com/CVE-2026-37709/): Snipe-IT has insecure permissions in file uploads (critical 9.8)
- [CVE-2026-86738](https://insights.sbomify.com/CVE-2026-86738/): Snipe-IT before 8.7.0 CSS Injection via Custom CSS (critical 9.3)
- [CVE-2026-116199](https://insights.sbomify.com/CVE-2026-116199/): Snipe-IT before 8.6.3 Authentication Bypass via Google SSO Callback (critical 9.2)
- [CVE-2022-1380](https://insights.sbomify.com/CVE-2022-1380/): Stored Cross Site Scripting vulnerability in Item name parameter in snipe/snipe-it (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-55516 and fix it if it is affected.

What it is: CVE-2026-55516 is a high-severity missing authorization vulnerability in Snipeitapp Snipe-It, published on 10 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-55516 in the wild and no public exploit code.

Affected packages and fixed versions:
- snipe/snipe-it (Packagist): affected all versions; fixed in 8.6.2
- snipe/snipe-it (Packagist): affected all versions; fixed in 8.6.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-55516/ (Markdown: https://insights.sbomify.com/CVE-2026-55516/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-55516
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-55516
- OSV: https://osv.dev/vulnerability/CVE-2026-55516

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-55516/
Summaries are generated and may contain mistakes; the official description above is the record.