CVE-2026-86744: snipe-it before 8.7.0 Race Condition in Asset Checkout

Severity: low (CVSS 2.2 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.3% probability of exploitation in the next 30 days
Public exploit or detection template: yes
Published: 2026-09-09 · updated 2026-09-18
Weakness: CWE-362

Description

Snipe-IT 8.6.3 and earlier (and develop pre-release commits prior to the fix) contain a race condition in the asset checkout paths. Api\AssetsController::checkout() and Assets\AssetCheckoutController::store() call Asset::availableForCheckout() outside the mutation path and then invoke Asset::checkOut() without taking a row lock or re-checking availability, so two concurrent checkout requests for the same available asset can both observe it as available and both commit. This produces duplicate checkout-history rows, a doubled checkout_counter, and two CheckoutableCheckedOut events for a single-assignment asset, corrupting the audit trail and utilization/reconciliation reporting; the asset's final assigned_to remains singular, so the visible assignment stays intact. Exploitation requires an authenticated session holding the assets.checkout permission (or superuser) and precise concurrent timing. Fixed in 8.7.0.

Affected products

grokability snipe-it: before 8.7.0 — fixed in 8.7.0

How to fix

Upgrade to a fixed version: grokability snipe-it 8.7.0. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2026-86744 or the next vulnerability affects your stack