Is CVE-2026-55483 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-55483 being exploited in the wild.

How severe is CVE-2026-55483?

High severity, with a CVSS score of 8.8, published 19 August 2026.

Which products and versions are affected?

snipe/snipe-it (Packagist) < 8.6.0, ECOSYSTEM:introduced=0,fixed=8.6.0.

Is there a fix for CVE-2026-55483?

Yes. snipe/snipe-it (Packagist): upgrade to 8.6.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-55483 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-55483?

Check whether you run snipe/snipe-it (Packagist) or Snipeitapp Snipe-It at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-55483: Snipe-IT privilege escalation in UsersController user creation

Q: Is there a fix for CVE-2026-55483?

Yes. snipe/snipe-it (Packagist): upgrade to 8.6.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-55483 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-55483?

Check whether you run snipe/snipe-it (Packagist) or Snipeitapp Snipe-It at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-55483 · Severity: high · CVSS 8.8 · Published 2026-08-19

Snipe-IT, a popular open-source IT asset management system, contains a flaw that allows users with basic account creation permissions to grant themselves or others full administrative access. This could allow staff members in roles like HR or department leads to bypass security restrictions and gain total control over the asset management platform. An attacker with this level of access could modify sensitive inventory data, delete records, or compromise the integrity of the organization's asset tracking.

Technologies: snipe/snipe-it (Packagist), Snipeitapp Snipe-It. Vendors: Packagist, Snipeitapp.

Quick answers

Is CVE-2026-55483 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-55483 being exploited in the wild.
How severe is CVE-2026-55483?: High severity, with a CVSS score of 8.8, published 19 August 2026.
Which products and versions are affected?: snipe/snipe-it (Packagist) < 8.6.0, ECOSYSTEM:introduced=0,fixed=8.6.0.
Is there a fix for CVE-2026-55483?: Yes. snipe/snipe-it (Packagist): upgrade to 8.6.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-55483 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-55483?: Check whether you run snipe/snipe-it (Packagist) or Snipeitapp Snipe-It at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

snipe/snipe-it (Packagist): upgrade to 8.6.0 or later
```
composer require snipe/snipe-it:^8.6.0
```

Technical details

A privilege escalation vulnerability exists in the `store()` method of both the web and API `UsersController` in Snipe-IT. While the application correctly strips 'superuser' permissions when a non-superuser creates a new account, it fails to perform a similar check for 'admin' permissions. Consequently, any authenticated user possessing the `users.create` permission can create a new user account and assign it full administrative privileges. This is classified as a missing authorization check (CWE-862). The vulnerability is addressed in version 8.6.0.

Affected products

Grokability Snipe-IT < 8.6.0

Identifiers

CVE-2026-55483
GHSA-hf68-g98v-wp9g

Timeline

2026-06-12: disclosed
2026-06-23: advisory: GitHub Advisory published
2026-06-23: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.