Answer in brief
CVE-2026-63493 records a High severity (CVSS 8.6) vulnerability in Snipe-IT: 2FA bypass via the API token flow. The current sources do not mark it as known exploited. The current feed maps snipe/snipe-it (composer), grokability/snipe-it (generic), snipe/snipe-it (packagist). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.6. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps snipe/snipe-it (composer), grokability/snipe-it (generic), snipe/snipe-it (packagist). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| snipe/snipe-itcomposer | <8.7.0 | 8.7.0 |
| grokability/snipe-itgeneric | <8.7.0 | 8.7.0 |
| snipe/snipe-itpackagist | >=0 <8.7.0 | 8.7.0 |
Published upstream
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 25, 2026
Snipe-IT is an IT asset/license management system. Prior to 8.7.0, a password-authenticated session for an account with self.api permission can reach the personal-access-token API flow before completing the account's second-factor challenge because CheckForTwoFactor is enforced in the web middleware group but not the API middleware group. The advisory states that the resulting persistent API token can read and modify resources with the victim's permissions and, for an administrator, can reach the users/two_factor_reset endpoint. Resetting the administrator's enrolled second factor allows the password-holding attacker to enroll an attacker-controlled factor, take over the administrator's web account, and lock out the legitimate user. The token does not create a web session, but it provides broad API access while the same browser session remains blocked at the two-factor page. This vulnerability is fixed in 8.7.0.
Quoted source text, attributed separately from HOL analysis.