# CVE-2026-48493: Snipe-IT Vulnerable to Privilege Escalation for self via API Permissions Assignment

> A user with edit permissions can escalate privileges via API to gain unauthorized access to assets and reports.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Jun 2026
- **Updated:** 25 Jun 2026
- **Also known as:** GHSA-52fw-7fw2-fmv5

## What is CVE-2026-48493?

CVE-2026-48493 is a medium-severity vulnerability in Snipeitapp Snipe-It, published on 23 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Snipe-IT is an IT asset/license management system. In versions prior to 8.6.0, a user with only users.edit can send a PATCH to /api/v1/users/{their_own_id} and grant themselves any permission except admin and superuser — for example `assets.view`, `assets.create`, `reports.view`, import, etc. The issue is patched in version 8.6.0.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-48493?

2 open source packages ship an affected version, including snipe/snipe-it. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `snipe/snipe-it` | Packagist | All versions | 8.6.0 |
| `snipe/snipe-it` | Packagist | All versions | 8.6.0 |

Products: Snipeitapp Snipe-It.

## How do I fix CVE-2026-48493?

Upgrade snipe/snipe-it to 8.6.0 or later.

## Is CVE-2026-48493 being exploited?

There is no known exploitation of CVE-2026-48493 in the wild and no public exploit code.

## Other vulnerabilities in Snipeitapp Snipe-It

- [CVE-2025-63601](https://insights.sbomify.com/CVE-2025-63601/): File upload in n/a (critical 9.9)
- [CVE-2026-37709](https://insights.sbomify.com/CVE-2026-37709/): Snipe-IT has insecure permissions in file uploads (critical 9.8)
- [CVE-2026-86738](https://insights.sbomify.com/CVE-2026-86738/): Snipe-IT before 8.7.0 CSS Injection via Custom CSS (critical 9.3)
- [CVE-2026-116199](https://insights.sbomify.com/CVE-2026-116199/): Snipe-IT before 8.6.3 Authentication Bypass via Google SSO Callback (critical 9.2)
- [CVE-2022-1380](https://insights.sbomify.com/CVE-2022-1380/): Stored Cross Site Scripting vulnerability in Item name parameter in snipe/snipe-it (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48493 and fix it if it is affected.

What it is: CVE-2026-48493 is a medium-severity vulnerability in Snipeitapp Snipe-It, published on 23 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-48493 in the wild and no public exploit code.

Affected packages and fixed versions:
- snipe/snipe-it (Packagist): affected all versions; fixed in 8.6.0
- snipe/snipe-it (Packagist): affected all versions; fixed in 8.6.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48493/ (Markdown: https://insights.sbomify.com/CVE-2026-48493/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48493
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48493
- OSV: https://osv.dev/vulnerability/CVE-2026-48493

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48493/
Summaries are generated and may contain mistakes; the official description above is the record.