CVE-2026-86744

LOW
Published Sep 9, 2026 Modified Sep 14, 2026 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.

Is your site exposed to CVE-2026-86744?

Run a free security scan — no signup, results in seconds.

CVSS v3.1 Score

2.2
LOW
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:N

EPSS — Exploit Prediction

0.0021
Probability of exploitation
0.12%
Percentile rank

EPSS estimates the probability that this vulnerability will be exploited in the wild within the next 30 days. A higher score means more likely to be exploited.

Weakness Type (CWE)

CWE-362 CWE-362

Affected Products

Vendor Product
snipeitapp snipe-it

References

Frequently Asked Questions

What is CVE-2026-86744? +
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. It has a CVSS v3.1 base score of 2.2 (LOW).
How severe is CVE-2026-86744? +
CVE-2026-86744 has a CVSS v3.1 score of 2.2 out of 10, rated LOW. This is a low-severity vulnerability with limited impact. The EPSS score is 0.0021, placing it in the 0th percentile for exploitation probability.
What products are affected by CVE-2026-86744? +
CVE-2026-86744 affects products from snipeitapp, specifically: snipe-it. Check the affected products table above for specific version ranges.
How do I check if I'm vulnerable to CVE-2026-86744? +
You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.

Related Vulnerabilities

Don't wait for an exploit

Scan your website for vulnerabilities like CVE-2026-86744 — free, no signup required.