# CVE-2026-86733: Snipe-IT before 8.7.0 Remote Code Execution via Backup Restore

> Authenticated superadministrators can execute arbitrary OS commands via crafted backup restores due to missing binary mode in MySQL client invocation.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-f9ch-gg2x-p955, GHSA-x53f-48vj-c5fc

## What is CVE-2026-86733?

CVE-2026-86733 is a high-severity command injection vulnerability in Snipeitapp Snipe-It, published on 8 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Snipe-IT before 8.7.0 streams the SQL entry from an uploaded backup archive directly into the MySQL/MariaDB command-line client (`mysql`) without the --binary-mode flag, so the client interprets lines beginning with backslash commands such as `\!` as local shell commands. An authenticated superadministrator who uploads a crafted ZIP backup (POST /admin/backups/upload) and triggers a restore (POST /admin/backups/restore/{filename}) without the optional `clean` sanitizer parameter — which is not applied by default because DB_SANITIZE_BY_DEFAULT is false — can execute arbitrary OS commands as the web application's operating-system user, exposing application secrets (including database credentials and APP_KEY) and allowing modification of application-writable files and data. Version 8.7.0 adds the --binary-mode flag to the client invocation.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Snipeitapp Snipe-It.

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

No fix has been published for CVE-2026-86733 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-86733 being exploited?

There is no known exploitation of CVE-2026-86733 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-86733 and fix it if it is affected.

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

Affected product: Snipeitapp Snipe-It. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-86733/ (Markdown: https://insights.sbomify.com/CVE-2026-86733/index.md)
```

## Sources

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

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