CVE-2026-55462

CVE-2026-55462 is a medium-severity incorrect authorization vulnerability in snipe/snipe-it (composer), affecting versions <= 8.6.0. It is fixed in 8.6.1.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Snipe-IT has an authorization bypass on print inventory page

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

  1. Create a user with only users.view.

  2. Create a target user with assigned license/accessory/consumable records containing recognizable test values.

  3. Log in as the users.view-only user.

  4. Confirm direct module access is denied:

GET /licenses
GET /accessories
GET /consumables

Observed for each:

HTTP/1.1 403 Forbidden
  1. 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 OK

The 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.

  1. 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 OK

The 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.

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.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

CVE-2026-55462 has a CVSS score of 4.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (8.6.1); upgrading removes the vulnerable code path.

Affected versions

snipe/snipe-it (<= 8.6.0)

Security releases

snipe/snipe-it → 8.6.1 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Patched in 374f426f0c

Frequently Asked Questions

  1. What is CVE-2026-55462? CVE-2026-55462 is a medium-severity incorrect authorization vulnerability in snipe/snipe-it (composer), affecting versions <= 8.6.0. It is fixed in 8.6.1. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
  2. How severe is CVE-2026-55462? CVE-2026-55462 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of snipe/snipe-it are affected by CVE-2026-55462? snipe/snipe-it (composer) versions <= 8.6.0 is affected.
  4. Is there a fix for CVE-2026-55462? Yes. CVE-2026-55462 is fixed in 8.6.1. Upgrade to this version or later.
  5. Is CVE-2026-55462 exploitable, and should I be worried? Whether CVE-2026-55462 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2026-55462 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2026-55462? Upgrade snipe/snipe-it to 8.6.1 or later.

Stop the waste.
Protect your environment with Kodem.

Get a personalized demo
Get a personalized demo