CVE-2026-44832: Snipe-IT: Privilege Escalation via API Permissions Assignment
Snipe-IT is an IT asset/license management system. Prior to 8.4.1, aAn authenticated user with only users.edit permission can escalate their own privileges to admin by sending a PATCH request to /api/v1/users/{id} with permissions[admin]=1. The API controller only strips the superuser key from the permissions array, allowing admin and all other permission keys to be set by any user who can update users. This vulnerability is fixed in 8.4.1.
Security readout for executives and security teams
Plain-English summary
CVE-2026-44832 lets a low-privileged authenticated Snipe-IT user with user-editing rights make themselves an admin through the API. For organizations using Snipe-IT to track assets and licenses, this can expose sensitive inventory data and allow unauthorized administrative control. The vendor advisory says versions before 8.4.1 are affected and 8.4.1 fixes it.
Executive priority
Prioritize remediation for any Snipe-IT instance where non-admin staff can edit users. This is a high-impact privilege escalation affecting administrative control over asset management data, but available evidence does not indicate active exploitation.
Technical view
In Snipe-IT before 8.4.1, the API user update path improperly handles permission assignment. A user with only users.edit can update their own permissions because the controller strips only the superuser key, not admin or other permission keys. This is categorized as CWE-281 and CWE-863, with CVSS 4.0 score 8.7.
Likely exposure
Exposure is limited to Snipe-IT deployments before 8.4.1 where authenticated users have users.edit permission. Internet exposure increases risk, but authentication and a specific permission are required.
Exploitation context
The provided sources do not show active exploitation, and this CVE is not listed as KEV in the bundle. Exploitation requires an authenticated account with users.edit permission and access to the Snipe-IT API.
Researcher notes
The key flaw is insufficient authorization enforcement during API permission updates. The source bundle states only superuser is stripped from the permissions array, leaving admin and other permission keys assignable. Validate behavior only in authorized test environments and avoid publishing weaponized request details.
Mitigation direction
Upgrade Snipe-IT to version 8.4.1 or later.
Restrict users.edit permission to trusted administrators only.
Review vendor advisory and commit for implementation details.
Audit recent permission changes and unexpected admin accounts.
Reduce external API exposure where operationally feasible.
Validation and detection
Inventory all Snipe-IT instances and confirm installed versions.
Identify users or roles granted users.edit permission.
Review audit logs for self-directed permission changes.
Check for newly created or unexpected admin accounts.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-281: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
CWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-281 · source CWE mapping
Improper Preservation of Permissions
Improper Preservation of Permissions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.