CVE-2026-55476 Snipe-IT vulnerability
Snipe-IT is an IT asset/license management system. Prior to 8.6.0, POST /account/request/{itemType}/{itemId}/{cancel_by_admin?}/{requestingUser?} accepts cancel_by_admin as a URL path segment without sufficient authorization, allowing an authenticated user to supply a victim user ID and silently cancel that user’s pending asset requests. This issue is fixed in version 8.6.0.
Quick answer
Snipe-IT should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- Snipe-IT before 8.6.0
Fixed versions
- 8.6.0
How to fix it
CVE-2026-55476 affects Snipe-IT asset management deployments where asset request cancellation accepts cancel_by_admin and requestingUser route parameters without sufficient authorization. Prioritize shared, multi-company, or internet-facing Snipe-IT instances because the issue can alter assets, users, permissions, or expose data depending on the affected endpoint. Upgrade Snipe-IT to 8.6.0 or a later supported release. Limit request cancellation routes to trusted roles until patched.
- Inventory all Snipe-IT production, staging, and internal asset-management deployments, including containers and hosted instances.
- Identify versions before the fixed Snipe-IT release for CVE-2026-55476: 8.6.0.
- Upgrade Snipe-IT to 8.6.0 or a later supported release, then run database migrations and application cache clears required by the deployment method.
- Limit request cancellation routes to trusted roles until patched.
- Review Snipe-IT roles, granular permissions, API tokens, Full Multiple Companies Support settings, and asset-management workflows for excessive privilege.
- Review web, API, audit, and application logs for suspicious endpoint use, unexpected permission changes, cross-company records, deleted users, or modified assets.
- If unauthorized changes are suspected, revoke tokens, rotate affected credentials, restore modified records from audit history or backup, and preserve evidence.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm every Snipe-IT node reports version 8.6.0 or a later supported release.
- Confirm a regular authenticated user cannot cancel another user’s pending asset request.
- Confirm API and UI permissions enforce company scope and object-level authorization for the affected workflow.
- Run regression checks against the affected endpoint and confirm unauthorized requests fail without changing data.
- Document patched versions, migration status, permission tests, reviewed logs, and any corrective data repairs.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-55476?
Snipe-IT versions listed as affected should be reviewed: Snipe-IT before 8.6.0.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.