Vulnerability · Published Sep 9, 2026 · Assigned by VulnCheck

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

Low 2.2

In plain English

A low-severity race condition in snipe-it from grokability. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 19% of all known vulnerabilities).

Severity (CVSS 3.1)2.2Low

Exploit odds (30 days)0.3%top 80.5% of all CVEs

Exploited in the wildNo reportsCISA SSVC: none

Attack toolingNoneno public tooling known

Official 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 (as reported)

Vendor	Product	Versions
grokability	snipe-it	0 – before 8.7.0

Weakness: CWE-362 · Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:N

References

GitHub Security Advisory (GHSA-h992-9438-26v8) vendor-advisory
Patch Commit patch
VulnCheck Advisory: snipe-it before 8.7.0 Race Condition in Asset Checkout third-party-advisory