Quick answers
- Is CVE-2026-55475 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-55475 being exploited in the wild.
- How severe is CVE-2026-55475?
- Medium severity, with a CVSS score of 5.7, published 10 July 2026.
- Which products and versions are affected?
- snipe/snipe-it (Packagist) <= 8.6.0, ECOSYSTEM:introduced=0,fixed=8.6.1.
- Is there a fix for CVE-2026-55475?
- Yes. snipe/snipe-it (Packagist): upgrade to 8.6.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-55475 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-55475?
- 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.1 or later
composer require snipe/snipe-it:^8.6.1
Technical details
This vulnerability is an incorrect authorization (CWE-863) flaw in Snipe-IT's Importer API endpoint. An authenticated user with CSV import capabilities can arbitrarily overwrite the `created_by` field of imported assets by sending a crafted request with a valid API key, bypassing proper field validation and authorization checks. The attack requires network access to the API endpoint and user interaction (crafting the import), but the attacker must already possess valid API credentials and import permissions. This allows attackers to falsely attribute asset creation to other users, compromising audit trails and accountability. The vulnerability was patched in version 8.6.1; all versions 8.6.0 and earlier are affected.
Affected products
- Grokability Snipe-IT <= 8.6.0
Identifiers
- CVE-2026-55475
- GHSA-5wx7-xq8j-v4qm
Timeline
- 2026-06-24: disclosed
- 2026-06-24: patched: Version 8.6.1 released
- 2026-08-28: advisory