CVE-2026-86744 PUBLISHED

snipe-it before 8.7.0 Race Condition in Asset Checkout

Assigner: VulnCheck
Reserved: 08.09.2026 Published: 09.09.2026 Updated: 09.09.2026

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.

Metrics

CVSS Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
CVSS Score: 2.1

Product Status

Vendor grokability
Product snipe-it
Versions Default: unaffected
  • affected from 0 to 8.7.0 (excl.)
  • Version 8.7.0 is unaffected

Credits

  • PizzaStev3 reporter
  • snipe finder
  • christopherfi-dev finder

References

Problem Types

  • Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') CWE