CVE-2026-55462: Snipe-IT has an authorization bypass on print inventory page
Impact An authenticated user with only users.view can open another user's detail page and see assigned license, accessory, and consumable data even though the same account is denied direct access to the Licenses, Accessories, and Consumables modules. The leaked data includes software license names, purchase order/order values, accessory and consumable names, assignment notes, and purchase costs.
Published Aug 28, 2026
Affected packages
snipe/snipe-it
- Ecosystem
- Composer (PHP)
- Affected
- <= 8.6.0
- Fixed in
- 8.6.1
- Check
composer show snipe/snipe-it
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
An authenticated user with only users.view can open another user's detail page and see assigned license, accessory, and consumable data even though the same account is denied direct access to the Licenses, Accessories, and Consumables modules. The leaked data includes software license names, purchase order/order values, accessory and consumable names, assignment notes, and purchase costs.
Attacker Model
Authenticated user with only:
{"users.view":"1"}The attacker does not have:
{
"licenses.view": "1",
"accessories.view": "1",
"consumables.view": "1",
"assets.view": "1"
}Affected Component
app/Http/Controllers/Users/UsersController.php
resources/views/users/view.blade.php
resources/views/users/print.blade.php
- Endpoints:
GET /users/{user}
GET /users/{user}/print
Root Cause
UsersController::show() authorizes only viewing the user, then loads inventory relationships:
$this->authorize('view', $user);
$user = User::with([
'consumables',
'accessories',
'licenses',
'userloc',
'groups',
])resources/views/users/view.blade.php renders those relationships without checking the corresponding module permissions. The license table renders name, purchase cost, purchase order, and order number. The accessory and consumable tables render item names, notes, and unit costs.
UsersController::printInventory() similarly authorizes only view on User::class and the target user, then renders resources/views/users/print.blade.php, which outputs assigned inventory names.
Proof of Concept
- Create a user with only
users.view.
- Create a target user with assigned license/accessory/consumable records containing recognizable test values.
- Log in as the
users.view-only user.
- Confirm direct module access is denied:
GET /licenses
GET /accessories
GET /consumablesObserved for each:
HTTP/1.1 403 Forbidden- Request the target user's page:
GET /users/<target-user-id> HTTP/1.1
Host: <snipe-it-host>
Cookie: snipeit_session=<attacker-session>Observed:
HTTP/1.1 200 OKThe response contained assigned inventory data from modules the attacker could not directly access, including license name, purchase order/order values, accessory name/note/cost, and consumable name/note/cost.
- Request the print view:
GET /users/<target-user-id>/print HTTP/1.1
Host: <snipe-it-host>
Cookie: snipeit_session=<attacker-session>Observed:
HTTP/1.1 200 OKThe response contained assigned inventory names.
Evidence
The users.view-only test account was confirmed to lack direct inventory permissions:
{
"has_users_view": true,
"has_licenses_view": false,
"has_accessories_view": false,
"has_consumables_view": false,
"has_assets_view": false
}Direct access to /licenses, /accessories, and /consumables returned 403 Forbidden.
The same account received 200 OK from /users/<target-user-id> and the response included assigned inventory data that should have been protected by the corresponding inventory module permissions.
Negative Controls
Denied direct module responses did not include the test inventory strings. The same data was only disclosed through the user detail and user print views.
Impact
Organizations may use separate permissions to allow HR/helpdesk-style users to view people records without exposing license, accessory, or consumable inventories and cost/order metadata. This issue bypasses those module-specific permissions and leaks assigned inventory information through the user view.
Patches
Patched in 374f426f0c
Credited to mamdouhmahfouz.
References
- https://github.com/grokability/snipe-it/security/advisories/GHSA-fc33-6w3q-538h
- https://nvd.nist.gov/vuln/detail/CVE-2026-55462
- https://github.com/grokability/snipe-it/commit/374f426f0c6bb7a4f129f7b85051cc1da753a0f5
- https://github.com/grokability/snipe-it/releases/tag/v8.6.2
- https://github.com/advisories/GHSA-fc33-6w3q-538h
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-62368
Snipe-IT: Stored XSS via Custom Field name in asset-list column headers
high8.1Sep 24, 2026CVE-2026-63493
Snipe-IT: 2FA bypass via the API token flow
high8.6Sep 24, 2026CVE-2026-63498
Snipe-IT: Stored XSS via Inline XML Rendering in the Uploaded Files API
high8.7Sep 24, 2026CVE-2026-55452
Snipe-IT has CSV formula injection in Activity Report export
medium4.8Aug 28, 2026CVE-2026-55460
Snipe-IT has an authorization bypass on bulk editing users
high7.1Aug 28, 2026CVE-2026-55461
Snipe-IT has an Open Redirect After User Edit
medium6.1Aug 28, 2026
