Quick answers
- Is CVE-2026-55643 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-55643 being exploited in the wild.
- How severe is CVE-2026-55643?
- 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.3, ECOSYSTEM:introduced=0,fixed=8.6.3.
- Is there a fix for CVE-2026-55643?
- Yes. snipe/snipe-it (Packagist): upgrade to 8.6.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-55643 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-55643?
- 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.3 or later
composer require snipe/snipe-it:^8.6.3
Technical details
The vulnerability is a broken authorization/privilege escalation issue (CWE-863) stemming from inconsistent authorization checks across multiple API endpoints and web routes. While the instance-level authorization function (isCurrentUserHasAccess) correctly enforces tenant boundaries, several endpoints—including GET /api/v1/users, GET /api/v1/users/{id}/licenses, POST /users/bulkeditsave, and POST /users/merge—rely on class-level permissions or overly broad scoped queries that fail to filter out users with company_id = null. A company-scoped attacker with low privileges can exploit this via network access (no special user interaction required) to read PII and license data, modify user profiles, soft-delete accounts, and transfer assets. The vulnerability affects Snipe-IT versions prior to 8.6.3 and has been patched in commit fbe05a8.
Affected products
- Grokability Snipe-IT < 8.6.3
Identifiers
- CVE-2026-55643
- GHSA-c6w2-j4wq-mvwg
Timeline
- 2026-08-19: disclosed: Published to GitHub Advisory Database
- 2026-08-19: patched: Patched in version 8.6.3 via commit fbe05a8