Skip to main content
VulnerabilityPublished

CVE-2026-55643: grokability snipe-it · Incorrect Authorization

Affects grokability snipe-itSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.6 High : upgrade to 8.6.3 soon.

Data as of 17 Nov 2026, 20:25 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Aug 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 17 Nov 2026.

What to do

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

Affected software

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

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

AI-suggested

Upgrade Snipe-IT to version 8.6.3 or later, where this authorization issue is fixed. No other mitigation or workaround is documented. Patch status is not explicitly stated in the input data but the description confirms the issue is fixed in 8.6.3.

Description

Snipe-IT is an IT asset/license management system. Prior to 8.6.3, a company-scoped user in FMCS floater mode can access users whose company_id is null because broad API queries and bulk web actions do not consistently apply isCurrentUserHasAccess. The /api/v1/users and /api/v1/users/{id}/licenses endpoints can expose personal data and assigned licenses, /users/bulkeditsave can modify out-of-scope profiles, and /users/merge can soft-delete users and transfer assigned assets. This issue is fixed in version 8.6.3.

References

Community reviews

Loading reviews…