# CVE-2026-55516: Grokability Snipe-IT authorization bypass in maintenance API

Source: https://junglewise.ai/threats/cve-2026-55516-grokability-snipe-it-authorization-bypass-in-maintenance-api  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-07-10. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2026-55516 · Severity: high · CVSS 7.7 · Published 2026-07-10

Snipe-IT is an asset management system used by organizations to track and maintain IT equipment across multiple departments or subsidiary companies. In multi-company deployments, this vulnerability allows an authenticated employee from one company to tamper with maintenance records of assets belonging to a different company. An attacker could corrupt maintenance histories, warranty records, and cost tracking data on victim assets, undermining audit compliance and operational integrity.

Technologies: [snipe/snipe-it (Packagist)](https://junglewise.ai/threats/technologies/snipe-snipe-it). Vendors: [Packagist](https://junglewise.ai/threats/vendors/packagist).

## Quick answers

**Is CVE-2026-55516 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-55516 being exploited in the wild.

**How severe is CVE-2026-55516?** High severity, with a CVSS score of 7.7, 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-55516?** 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-55516 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-55516?** 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

  ```sh
  composer require snipe/snipe-it:^8.6.2
  ```


## Technical details

The vulnerability exists in the API endpoint `PATCH /api/v1/maintenances/{maintenance_id}` (and likely `PUT` variant) in `app/Http/Controllers/Api/MaintenancesController.php`. The application correctly validates that the user has access to the current maintenance record's asset before allowing the update, but then uses `$maintenance->fill($request->all())` and `$maintenance->save()` without re-validating the newly supplied `asset_id` against the user's company scope. Since `asset_id` is fillable on the maintenance model, an authenticated user with maintenance-update permissions can change the asset_id to point to any asset, including those outside their authorized company boundary. The attack requires a valid API token, maintenance-update permission, and access to an existing maintenance record in the user's own company, but does not require access to the target asset. This is a classic authorization-bypass-through-user-controlled-key flaw (CWE-639) that breaks tenant isolation in multi-company environments.

## Affected products

- grokability snipe-it <= 8.6.1

## Identifiers

- CVE-2026-55516
- GHSA-575r-357h-fhch

## Timeline

- 2026-06-24: disclosed: Published on GitHub Advisory Database
- 2026-07-10: advisory: Published to NVD
- 2026-08-28: patched: Version 8.6.2 released with fix

## References

- [https://api.github.com/users/5h1kh4r](https://api.github.com/users/5h1kh4r)
- [https://github.com/5h1kh4r](https://github.com/5h1kh4r)
- [https://api.github.com/users/5h1kh4r/gists%7B/gist_id%7D](https://api.github.com/users/5h1kh4r/gists%7B/gist_id%7D)
- [https://api.github.com/users/5h1kh4r/repos](https://api.github.com/users/5h1kh4r/repos)
- [https://avatars.githubusercontent.com/u/99708506?v=4](https://avatars.githubusercontent.com/u/99708506?v=4)
- [https://api.github.com/users/5h1kh4r/events%7B/privacy%7D](https://api.github.com/users/5h1kh4r/events%7B/privacy%7D)

## Related threats

- [Snipe-IT stored XSS via inline XML rendering in uploaded files API](https://junglewise.ai/threats/cve-2026-63498-snipe-it-stored-xss-via-inline-xml-rendering-in-uploaded-files)
- [Snipe-IT 2FA bypass via API token flow](https://junglewise.ai/threats/cve-2026-63493-snipe-it-2fa-bypass-via-api-token-flow)
- [Snipe-IT stored XSS in custom field names](https://junglewise.ai/threats/cve-2026-62368-snipe-it-stored-xss-in-custom-field-names)
- [Snipe-IT stored DOM XSS via table selected-count IDs](https://junglewise.ai/threats/cve-2026-61807-snipe-it-stored-dom-xss-via-table-selected-count-ids)
- [Snipe-IT maintenance record disclosure via missing authorization](https://junglewise.ai/threats/cve-2026-55703-snipe-it-maintenance-record-disclosure-via-missing-authorization)