---
id: "CVE-2026-116198"
kind: "vulnerability"
aliases: ["CVE-2026-116198"]
title: "Snipe-IT: API asset creation stores encrypted custom fields as plaintext"
severity: "medium"
cvss: 5.3
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["api", "package", "php", "self-hosted", "snipe-it"]
not_affected_if: ["api-disabled", "managed-hosting-patched", "no-encrypted-custom-fields"]
published_at: "2026-10-25T14:17:00+00:00"
first_seen_at: "2026-10-25T14:41:23+00:00"
updated_at: "2026-10-25T14:43:03+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-116198", "first_seen_at": "2026-10-25T14:41:23+00:00"}]
---

# Snipe-IT: API asset creation stores encrypted custom fields as plaintext

Snipe-IT before 8.7.0 accepts asset creation through its API from users who lack the encrypted custom fields permission, and it saves values for encrypted-flagged custom fields in plaintext. An attacker with a low-privilege API token can get sensitive values into the database unencrypted, where they can be read from backups, replicas or direct database access.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed Snipe-IT version, for example in the app's `composer.json` or the admin footer, and see whether it is below `8.7.0`
- Review which API tokens and users lack the `assets.view.encrypted_custom_fields` permission and whether they can create assets
- unknown

## Fix

- Upgrade Snipe-IT to `8.7.0` or later
- Rotate any sensitive values stored in encrypted-flagged custom fields that were written through the API before the upgrade, and purge unencrypted copies from backups as needed

## Timeline

- 2026-10-25T14:41:23+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-116198

## From the sources

Snipe-IT before 8.7.0 contains a missing encryption vulnerability in Api\AssetsController::store that writes plaintext into encrypted-flagged custom-field columns when callers lack assets.view.encrypted_custom_fields. Authenticated API users without that permission can create assets whose sensitive custom-field values persist unencrypted in the database, exposing them through backups, replicas, or direct database access.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_