CVE-2026-55843: Snipe-IT: Improper Privilege Management

Published Jul 10, 2026
·
Updated

Impact

The update() method in UsersController passes the permission request field unconditionally to NormalizePermissionsPayloadAction, which returns an empty array when the field is absent. The result is passed to PreserveUnauthorizedPrivilegedPermissionsAction, which selectively restores only the superuser key (when the editor is not a superuser) and the admin key (when the editor is neither admin nor superuser). All other permissions — including the admin flag itself when the editing user is an admin — are discarded and $user->permissions is overwritten with the sparse result.

The canEditAuthFields gate permits admins to update other non-superuser accounts (including other admins). When an admin sends a PUT /users/{id} request for another admin without including the permission field, the target's admin flag and all granular permissions are permanently destroyed. The target loses administrative access entirely with no error, warning, or out-of-band notification.

A secondary, lower-impact path exists for non-admin users holding the users.edit permission: they may target regular (non-admin, non-superuser) accounts and wipe all granular permissions in the same way.

Patches Patched in https://github.com/grokability/snipe-it/commit/1cff2d67aabd00ee51d864c1d7fb717494c1d6ad

Other sources

Snipe-IT is an IT asset/license management system. Prior to 8.6.0, UsersController::update() passes a missing permission request field through NormalizePermissionsPayloadAction and PreserveUnauthorizedPrivilegedPermissionsAction in a way that can overwrite a target user’s permissions with a sparse result, allowing an administrator updating another administrator, or a user with users.edit updating a regular account, to remove the target’s administrative or granular permissions. This issue is fixed in version 8.6.0.

MITRE

Affected Software

3 affected componentsFixes available
Snipe-IT Snipe-IT<8.6.0
Snipeitapp Snipe-it<8.6.0
composer/snipe/snipe-it<8.6.0
8.6.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/snipe/snipe-it to a version that resolves this vulnerability.

    Fixed in 8.6.0
  2. Upgrade

    Upgrade grokability/snipe-it to a version that resolves this vulnerability.

    Fixed in 8.6.0
  3. Operational

    After upgrading to 8.6.0, review affected user accounts and restore the target users’ `admin` flag and granular permissions if they were removed by a prior `PUT /users/{id}` request that omitted the `permission` field.

Event History

Jul 10, 2026
CVE Published
via MITRE·06:33 PM
Data Sourced
via MITRE·06:33 PM
DescriptionWeakness
Data Sourced
via NVD·07:17 PM
RemedyDescriptionSeverityWeaknessAffected Software
Aug 28, 2026
Advisory Published
via GitHub·10:37 PM
Data Sourced
via GitHub·10:37 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-55843?

CVE-2026-55843 has a risk score of 51, indicating a moderate level of severity.

2

What kind of vulnerability is identified in CVE-2026-55843?

CVE-2026-55843 is an improper privilege management vulnerability affecting Snipe-IT prior to version 8.6.0.

3

How do I fix CVE-2026-55843?

To mitigate CVE-2026-55843, upgrade Snipe-IT to version 8.6.0 or later.

4

What impact does CVE-2026-55843 have on Snipe-IT users?

CVE-2026-55843 can lead to unauthorized modification of user permissions, potentially compromising user access controls.

5

Who is affected by CVE-2026-55843?

Any user or system relying on Snipe-IT versions prior to 8.6.0 may be affected by CVE-2026-55843.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203