Skip to main content
VulnerabilityPublished Updated

CVE-2026-63493: grokability snipe-it · Authentication Bypass Using an Alternate Path or Channel

Affects grokability snipe-itSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.6 High : upgrade to 8.7.0 soon.

Data as of 8 Nov 2026, 23:24 UTC

CVSS 4.0 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 8.7.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.

What to do

Upgrade snipe-it and grokability/snipe-it to 8.7.0.

Affected software

ProductAffectedFixed in
grokabilitysnipe-itAffected
  • <8.7.0
Fixed in
  • 8.7.0
GitHubgrokability/snipe-itpkg:github/grokability/snipe-itOther threatsAffected
  • <8.7.0
Fixed in
  • 8.7.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability is fixed in Snipe-IT version 8.7.0. Users should upgrade to version 8.7.0 or later to remediate this issue. No additional mitigation steps are indicated beyond applying the official fix.

Description

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.

References

Community reviews

Loading reviews…