PatchSiren cyber security CVE debrief
CVE-2026-86759 grokability CVE debrief
CVE-2026-86759 is a high-severity vulnerability in Snipe-IT versions before 8.7.0, allowing any authenticated user to reassign arbitrary assets and modify audit logs via the POST /hardware/history endpoint. Attackers can submit a CSV file to reassign assets across companies and inject fraudulent audit trail entries, compromising inventory integrity and accountability.
- Vendor
- grokability
- Product
- snipe-it
- CVSS
- HIGH 7.1
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-09
- Original CVE updated
- 2026-09-16
- Advisory published
- 2026-09-09
- Advisory updated
- 2026-09-16
Who should care
Defenders responsible for Snipe-IT deployments should assess exposure and prioritize verification and remediation to prevent unauthorized asset reassignment and audit log tampering.
Why it matters
CVE-2026-86759 is a high-severity vulnerability in Snipe-IT that allows unauthorized asset reassignment and audit log tampering. Defenders should prioritize verification and remediation to prevent exploitation and potential impact on asset management and auditing processes.
- Compromised inventory integrity and accountability due to unauthorized asset reassignment
- Potential injection of fraudulent audit trail entries
- Need for verification of Snipe-IT version and remediation to prevent exploitation
- Potential impact on asset management and auditing processes
Technical summary
Snipe-IT versions before 8.7.0 fail to authorize the POST /hardware/history endpoint, allowing any authenticated user to reassign arbitrary assets and modify audit logs. Attackers can submit a CSV file to reassign assets across companies and inject fraudulent audit trail entries. Defenders should prioritize verifying and upgrading to Snipe-IT version 8.7.0 or later to prevent unauthorized asset reassignment and audit log tampering. This vulnerability has a high CVSS score of 7.1 and affects Snipe-IT deployments, emphasizing the need for prompt verification and remediation.
Defensive priority
Defenders should prioritize verifying and upgrading to Snipe-IT version 8.7.0 or later to prevent unauthorized asset reassignment and audit log tampering.
Recommended defensive actions
- Verify Snipe-IT version and upgrade to 8.7.0 or later if necessary
- Restrict access to the POST /hardware/history endpoint
- Monitor audit logs for suspicious activity
- Implement additional access controls and authentication measures
- 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.
Evidence notes
The CVE record and NVD entry provide details on the vulnerability, including its high CVSS score of 7.1 and affected versions of Snipe-IT. Vendor advisory and third-party advisory references are also available.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-86759 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-86759
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-86759 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-86759
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/grokability/snipe-it/security/advisories/GHSA-2232-926w-qvr9
[email protected] - Exploit, Vendor Advisory
-
Source reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/snipe-it-before-8.7.0-missing-authorization-via-asset-history-csv-importer
[email protected] - Third Party Advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.