All vulnerabilities

Servers and applications

CVE-2026-86757

Encrypted custom-field values were rendered as plaintext for some field types

Severity
High 7.1
Published
24 Aug 2026
Last changed
16 Sept 2026
Added to UpHeron
3 Nov 2026
Fixed in
8.7.0
Exploit chance
0.4% in the next 30 daysHigher than 31% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Missing authorization (CWE-862)
Attack
Over the network · Needs a user account · No user action needed
Attacker can
Read data
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Also known as
GHSA-j36v-ghpr-m963
Sources
NVD, Project advisories (GitHub)

Description

Snipe-IT gates read access to encrypted asset custom-field values behind a separate permission (assets.view.encrypted_custom_fields), so that a user who can edit or handle assets does not automatically get access to the encrypted content of custom-field columns. The gate is AssetPolicy::viewEncryptedCustomFields / Gate::allows('assets.view.encrypted_custom_fields', ...), and it is honored in every display path outside the form template. The API asset transformer, the audit-log transformer, the assets index datatable, the reports controller, and the asset show-page presenter all consult it before rendering the raw serial:

The form template resources/views/models/custom_fields_form.blade.php was written before that gate existed and never picked up the check for element types other than the plain text input. The template renders one of eleven branches depending on $field->element and $field->format, and five of them called Helper::gracefulDecrypt(...) unconditionally:

From grokability/snipe-it's security advisory. Shortened; the full text is there.

Workarounds

Until the patch is applied, deployments should restrict the assets.edit, assets.checkin, assets.checkout, and assets.audit permissions to the same roles that already hold assets.view.encrypted_custom_fields. There is no request-level workaround, since the leak is in the form-rendering path that every one of those workflows opens as its first step.

Workarounds as given by grokability/snipe-it's security advisory.

Affected software

SoftwareAffected versions
Snipe-ITServers and applications · cpe:a:snipeitapp:snipe-it
  • Every version before 8.7.0
Snipe-ITServers and applications · github:grokability/snipe-it
  • Every version before 8.7.0

About Snipe-IT

A free open source IT asset/license management system

From its GitHub repository.
Docker Hub pulls
29,869,543Docker Hub, 15 Nov 2026
GitHub stars
15,189GitHub, 15 Nov 2026
Forks
4,068GitHub, 15 Nov 2026
Latest release
v8.8.3GitHub, 15 Nov 2026
Released
22 Oct 2026GitHub
License
AGPL-3.0GitHub
First published on GitHub
12 Nov 2013GitHub

References

  • NVD https://nvd.nist.gov/vuln/detail/CVE-2026-86757
  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-86757
  • GitHub Advisory Database https://github.com/advisories/GHSA-j36v-ghpr-m963
  • github.com https://github.com/grokability/snipe-it/security/advisories/GHSA-j36v-ghpr-m963