# CVE-2026-116198: Snipe-IT missing encryption in API assets endpoint

Source: https://junglewise.ai/threats/cve-2026-116198-snipe-it-before-8-7-0-contains-a-missing-encryption  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-25. Updated: 2026-10-25  
License: CC BY 4.0 with a link back

CVE-2026-116198 · Severity: medium · CVSS 4.3 · Published 2026-10-25

Snipe-IT is an open-source asset tracking system that stores sensitive hardware and inventory information. Due to a code logic error, authenticated API users without certain permissions can create assets with sensitive custom fields that are stored unencrypted in the database, even though those fields are marked as encrypted. This exposes sensitive data through database backups, replicas, and direct database access.

Technologies: [Grokability Snipe-IT](https://junglewise.ai/threats/technologies/grokability-snipe-it). Vendors: [Grokability](https://junglewise.ai/threats/vendors/grokability).

## 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

## References

- [https://github.com/grokability/snipe-it/security/advisories/GHSA-jh4g-98fm-jcqc](https://github.com/grokability/snipe-it/security/advisories/GHSA-jh4g-98fm-jcqc)
- [https://www.vulncheck.com/advisories/snipe-it-before-8.7.0-missing-encryption-via-api-assetscontroller-store](https://www.vulncheck.com/advisories/snipe-it-before-8.7.0-missing-encryption-via-api-assetscontroller-store)

## Related threats

- [Snipe-IT LDAP StartTLS downgrade to cleartext](https://junglewise.ai/threats/cve-2026-116200-snipe-it-before-8-6-3-ignores-the-ldap-start-tls-return-value-in)
- [Snipe-IT authentication bypass in Google SSO callback](https://junglewise.ai/threats/cve-2026-116199-snipe-it-before-8-6-3-contains-an-authentication-bypass-in)
- [Snipe-IT server-side request forgery in webhook testing](https://junglewise.ai/threats/cve-2026-114064-snipe-it-before-8-7-0-contains-a-server-side-request-forgery)