CVE-2026-55519: grokability snipe-it · Improper Authorization
Affects grokability snipe-itSource CVE Database V5
Not known to be exploited · CVSS 5.4 Medium : upgrade to 8.4.1 when convenient.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 8.4.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 19 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 16 Nov 2026.
What to do
Upgrade snipe-it and grokability/snipe-it to 8.4.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| grokabilitysnipe-it | Affected
| Fixed in
|
GitHubgrokability/snipe-itpkg:github/grokability/snipe-itOther threats | Affected
| Fixed in
|
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.4.1 or later, where this improper authorization vulnerability has been fixed. No other mitigation is indicated or required according to the available data.
Description
Snipe-IT versions prior to 8.4.1 contain an improper authorization vulnerability that allows authenticated users with generic asset edit permissions to delete files attached to assets outside their ownership or company assignment. This is due to insecure direct object reference caused by authorization checks against the object class rather than the specific object instance. The issue is resolved in version 8.4.1.