CVE-2026-116198: grokability snipe-it · Missing Encryption of Sensitive Data
Affects grokability snipe-itSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium · fixed in 8.7.0 : update grokability snipe-it when convenient.
Data as of 10/25/2026, 16:50:55 UTC
- Patch
- Available – fixed in 8.7.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wild: no evidence on record.
Not in CISA KEV and no source reports exploitation
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 2026-10-25.
What to do
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
A fix is available in Snipe-IT version 8.7.0. Users should upgrade to version 8.7.0 or later to remediate this vulnerability. No additional mitigations are specified.
Description
Snipe-IT versions before 8.7.0 have a vulnerability where sensitive custom-field data can be stored unencrypted in the database if an authenticated API user without the appropriate permission creates assets. This occurs in the Api\AssetsController::store method, leading to plaintext storage of data that should be encrypted. The vulnerability exposes sensitive data through backups, replicas, or direct database access.
Impact
Sensitive data intended to be encrypted is stored in plaintext in the database, potentially exposing it to unauthorized access via backups, replicas, or direct database queries. This compromises the confidentiality of sensitive custom-field data for affected Snipe-IT instances where the vulnerability is present.