Skip to main content
VulnerabilityPublished

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

Affects grokability snipe-itSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.8 Medium : upgrade to 8.5.0 when convenient.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
5.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 8.5.0
CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:U/C:L/I:H/A: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.5.0.

Affected software

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

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.5.0 or later, where this authorization flaw has been fixed. No other mitigations are specified. Patch status is not explicitly stated but the fix is included in version 8.5.0.

Description

Snipe-IT is an IT asset/license management system. Prior to 8.5.0, a user who can edit other users can reset a superadmin's two-factor authentication through app/Http/Controllers/Api/UsersController.php postTwoFactorReset(). The endpoint authorizes update access but does not enforce canEditAuthFields before clearing two_factor_secret and two_factor_enrolled. This issue is fixed in version 8.5.0.

References

Community reviews

Loading reviews…