CVE-2026-55472 Snipeitapp CVE debrief

Who should care

Administrators and users of Snipe-IT, especially those with Full Multiple Companies Support and scope_locations_fmcs enabled, should be aware of this vulnerability and take steps to defend against it. This includes updating Snipe-IT to version 8.6.2 or later, reviewing and restricting API access to the location creation endpoint, and monitoring for suspicious location creation activity.

Technical summary

The vulnerability exists in the location creation endpoint of Snipe-IT's API. When Full Multiple Companies Support and scope_locations_fmcs are enabled, the endpoint fails to immediately return when detecting an invalid parent-child company mismatch. This allows for the creation of a child location under a parent location from a different company. The issue has been fixed in version 8.6.2. The vulnerability has a CVSS score of 4.3 and a severity of MEDIUM. Administrators and users of Snipe-IT should be aware of this vulnerability and take steps to defend against it.

Defensive priority

Medium priority should be given to updating Snipe-IT to version 8.6.2 or later, especially for users with Full Multiple Companies Support and scope_locations_fmcs enabled. Defenders should also review compensating controls for exposed systems while remediation is scheduled and verified, and check relevant monitoring, detection, and logs for exposed assets that need extra review.

Recommended defensive actions

• Update Snipe-IT to version 8.6.2 or later
• Review and restrict API access to the location creation endpoint
• Monitor for suspicious location creation activity
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record was published on 2026-07-10T19:17:24.920Z and has not been modified since then. The NVD entry is currently Analyzed. There is limited information available about the vulnerability beyond the official CVE record and NVD entry. Defenders should verify the affected scope and severity with the vendor and review the official advisory for guidance. The CVE record and NVD entry provide the most accurate and up-to-date information on this vulnerability.

Official resources