Quick answers
- Is CVE-2026-116198 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116198 being exploited in the wild.
- How severe is CVE-2026-116198?
- Medium severity, with a CVSS score of 4.3, published 25 October 2026.
- Which products and versions are affected?
- Grokability Snipe-IT before 8.7.0.
- Is there a fix for CVE-2026-116198?
- Yes: fixed in 8.7.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116198 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-116198?
- Check whether you run Grokability Snipe-IT at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 8.7.0
Technical details
The Api\AssetsController::store endpoint fails to enforce encryption for sensitive custom fields when the authenticated caller lacks the assets.view.encrypted_custom_fields permission. The encryption gate checks if a field is flagged for encryption but then fails to skip the field when permission is denied, instead writing the plaintext value directly to the database. This is a control flow bug where the update() method was correctly implemented with a continue statement, but store() was not.
Affected products
- Grokability Snipe-IT before 8.7.0
Timeline
- 2026-10-08: disclosed
- 2026-10-25: advisory