CVE-2026-86766: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') in grokability snipe-it
Snipe-IT versions up to and including 8.6.3 contain a race condition (TOCTOU) in the consumable checkout API endpoint (POST /api/v1/consumables/{consumable_id}/checkout). The requested quantity is validated against the number of remaining units before the database transaction begins, and the transaction then creates the checkout records without locking the consumable row or re-checking availability. An authenticated user with permission to check out consumables can submit concurrent checkout requests for the same consumable so that both requests pass the availability check and succeed, over-allocating stock and driving the remaining inventory negative (e.g., a consumable with 1 remaining unit ends at -1 after two concurrent 1-unit checkouts). The issue is fixed in 8.7.0, which re-fetches the parent row under lockForUpdate inside the transaction and re-validates availability.
AI Analysis
Technical Summary
CVE-2026-86766 describes a race condition (time-of-check to time-of-use) vulnerability in Snipe-IT versions up to and including 8.6.3. The flaw exists in the POST /api/v1/consumables/{consumable_id}/checkout endpoint where the requested quantity is validated against available stock before the database transaction begins. However, the transaction that creates the checkout records does not lock the consumable row or re-check availability, allowing multiple concurrent requests to pass the availability check and succeed. This leads to over-allocation of consumables and negative inventory counts. The vulnerability requires authenticated users with permission to check out consumables. The issue is resolved in version 8.7.0 by re-fetching the consumable row with a lockForUpdate inside the transaction and re-validating availability.
Potential Impact
An authenticated user with checkout permissions can exploit this race condition to over-allocate consumable stock, causing inventory counts to become inaccurate and negative. This can disrupt inventory management and potentially lead to resource shortages or accounting errors. There is no indication of privilege escalation or remote code execution. The CVSS 4.0 score is 7.1 (high severity) reflecting network attack vector, low attack complexity, no user interaction, and high impact on integrity.
Mitigation Recommendations
A fix is available in Snipe-IT version 8.7.0, which addresses the race condition by implementing row locking and re-validation of consumable availability within the database transaction. Users should upgrade to version 8.7.0 or later to remediate this vulnerability. No other mitigations are indicated.
CVE-2026-86766: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') in grokability snipe-it
Description
Snipe-IT versions up to and including 8.6.3 contain a race condition (TOCTOU) in the consumable checkout API endpoint (POST /api/v1/consumables/{consumable_id}/checkout). The requested quantity is validated against the number of remaining units before the database transaction begins, and the transaction then creates the checkout records without locking the consumable row or re-checking availability. An authenticated user with permission to check out consumables can submit concurrent checkout requests for the same consumable so that both requests pass the availability check and succeed, over-allocating stock and driving the remaining inventory negative (e.g., a consumable with 1 remaining unit ends at -1 after two concurrent 1-unit checkouts). The issue is fixed in 8.7.0, which re-fetches the parent row under lockForUpdate inside the transaction and re-validates availability.
CVSS v4.0
Score 7.1high
Affected software
pkg:github/grokability/snipe-itRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-86766 describes a race condition (time-of-check to time-of-use) vulnerability in Snipe-IT versions up to and including 8.6.3. The flaw exists in the POST /api/v1/consumables/{consumable_id}/checkout endpoint where the requested quantity is validated against available stock before the database transaction begins. However, the transaction that creates the checkout records does not lock the consumable row or re-check availability, allowing multiple concurrent requests to pass the availability check and succeed. This leads to over-allocation of consumables and negative inventory counts. The vulnerability requires authenticated users with permission to check out consumables. The issue is resolved in version 8.7.0 by re-fetching the consumable row with a lockForUpdate inside the transaction and re-validating availability.
Potential Impact
An authenticated user with checkout permissions can exploit this race condition to over-allocate consumable stock, causing inventory counts to become inaccurate and negative. This can disrupt inventory management and potentially lead to resource shortages or accounting errors. There is no indication of privilege escalation or remote code execution. The CVSS 4.0 score is 7.1 (high severity) reflecting network attack vector, low attack complexity, no user interaction, and high impact on integrity.
Mitigation Recommendations
A fix is available in Snipe-IT version 8.7.0, which addresses the race condition by implementing row locking and re-validation of consumable availability within the database transaction. Users should upgrade to version 8.7.0 or later to remediate this vulnerability. No other mitigations are indicated.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-09-08T11:33:02.642Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6aa164b9acd9273b496859bb
Added to database: 09/09/2026, 13:52:57 UTC
Last enriched: 09/09/2026, 14:07:23 UTC
Last updated: 09/09/2026, 19:47:48 UTC
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.