CVE-2026-116198

Snipe-IT before 8.7.0 Missing Encryption via Api AssetsController store

Published Oct 25, 2026 CVSS 4.0 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

Snipe‑IT before version 8.7.0 contains a flaw in the Api\AssetsController::store method that causes values written to custom‑field columns marked as encrypted to be stored in plain text. The unencrypted data remains in the database, making it accessible through backups, replicas, or direct database access. This creates a confidentiality risk, potentially exposing sensitive asset information to attackers with database or backup access.

Affected Systems

The issue affects the Snipe‑IT application, specifically all releases prior to 8.7.0. Users running these versions are susceptible if they employ the API to create assets containing sensitive custom‑field values.

Risk and Exploitability

The CVSS score of 5.3 indicates moderate impact; the EPSS score is unavailable and the vulnerability is not listed in CISA KEV. The likely attack vector is via authenticated API requests from users who lack the assets.view.encrypted_custom_fields permission. Once such users create assets, the data is written unencrypted and can be retrieved by anyone with database or backup access, leading to potential data exfiltration.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Snipe‑IT to version 8.7.0 or later to fix the missing encryption handling.
  • Limit API permissions: only users with assets.view.encrypted_custom_fields may create assets that contain sensitive custom‑field values, and consider restricting asset creation for users without that permission.
  • Audit the current database for plain‑text values in encrypted‑flagged custom‑field columns and either delete the sensitive data or apply a manual encryption process, ensuring backups and replicas are also updated.

Generated by OpenCVE AI on October 25, 2026 at 16:57 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title Snipe-IT before 8.7.0 Missing Encryption via Api AssetsController store
First Time appeared Snipeitapp
Snipeitapp snipe-it
Weaknesses CWE-311
CPEs cpe:2.3:a:snipeitapp:snipe-it:*:*:*:*:*:*:*:*
Vendors & Products Snipeitapp
Snipeitapp snipe-it
References
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N'}

cvssV4_0

{'score': 5.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-311

    Missing Encryption of Sensitive Data

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 29, 2026, 4:24 PM
Reserved
Oct 25, 2026, 12:27 PM
Status
Analyzed
Published
Oct 25, 2026, 2:17 PM
Modified
Oct 29, 2026, 5:18 PM