CVE-2026-86757: Missing Authorization in grokability snipe-it
Affects grokability snipe-itSource CVE Database V5
Not known to be exploited · CVSS 7.1 High.
Data as of 10/25/2026, 04:40:14 UTC
- Exploitation
Not in CISA KEV, no exploitation reported
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NWhat to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| grokabilitysnipe-it | Affected
| Fixed in
|
GitHubgrokability/snipe-itpkg:github/grokability/snipe-itOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Snipe-IT to version 8.7.0 or later where this authorization issue is fixed. Since the vulnerability is addressed in version 8.7.0, applying this official fix will remediate the issue. No additional mitigations are specified.
Description
CVE-2026-86757 is a high-severity vulnerability in Snipe-IT before version 8.7.0 where certain encrypted custom field values in asset form templates are accessible without proper authorization. Authenticated users with specific asset permissions can bypass intended permission checks and view plaintext encrypted data in listbox, textarea, markdown-textarea, and date/datetime picker elements.
Impact
Unauthorized disclosure of encrypted custom field values can occur to users who should not have access, potentially exposing sensitive information stored in asset management forms. This bypass affects users with certain asset-related permissions but lacking explicit permission to view encrypted custom fields, increasing the risk of data leakage within the organization.
Summary
Snipe-IT versions prior to 8.7.0 have a missing authorization control that allows authenticated users holding assets.edit, assets.checkin, assets.checkout, or assets.audit permissions to read plaintext values of encrypted custom fields in asset form templates. This occurs because the system fails to enforce the assets.view.encrypted_custom_fields permission when rendering these fields, enabling unauthorized access to sensitive encrypted data.