Quick answers
- Is CVE-2026-62368 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-62368 being exploited in the wild.
- How severe is CVE-2026-62368?
- High severity, with a CVSS score of 8.1, published 24 September 2026.
- Which products and versions are affected?
- snipe/snipe-it (Packagist) < 8.7.0, ECOSYSTEM:introduced=0,fixed=8.7.0.
- Is there a fix for CVE-2026-62368?
- Yes. snipe/snipe-it (Packagist): upgrade to 8.7.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-62368 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-62368?
- Check whether you run snipe/snipe-it (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- snipe/snipe-it (Packagist): upgrade to 8.7.0 or later
composer require snipe/snipe-it:^8.7.0
Technical details
The vulnerability is a stored cross-site scripting (XSS) flaw in the asset list column headers. A user with the "customfields.create" permission can create a custom field with an HTML/JavaScript payload in its name (e.g., `<img src=x onerror=alert(1)>`). When the asset list page (/hardware) is rendered, the field name is passed to the bootstrap-table JavaScript plugin via the data-columns attribute without proper escaping. The bootstrap-table plugin renders the header title unescaped because its global escape option defaults to false. The vulnerability requires the attacker to have "customfields.create" permission (which can be granted to non-superusers) and the target to associate the custom field with an asset model. No user interaction is required—the payload executes automatically on page load. The patch was released in commit 58754e4.
Affected products
- Grokability Snipe-IT before commit 58754e4e3b86b58a0c4523012ef04a2ae990d2c8
Identifiers
- CVE-2026-62368
- GHSA-p9h3-gvpq-5539
Timeline
- 2026-09-24: disclosed
- 2026-09-24: patched: commit 58754e4e3b86b58a0c4523012ef04a2ae990d2c8