# CVE-2026-86762: Snipe-IT before 8.7.0 Authentication Bypass via API Middleware

> Deactivated Snipe-IT users retain API access, allowing them to read/modify data and re-activate their accounts, bypassing deactivation controls.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Sep 2026
- **Updated:** 10 Sep 2026
- **Also known as:** GHSA-cj4w-vx6j-42rf, GHSA-qrxg-4hw7-jwqj

## What is CVE-2026-86762?

CVE-2026-86762 is a high-severity authentication bypass vulnerability in Snipeitapp Snipe-It, published on 9 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Snipe-IT before 8.7.0 does not apply the CheckUserIsActivated middleware to the `api` middleware group in app/Http/Kernel.php, and deactivating a user does not revoke that user's Passport personal access tokens. As a result, although a deactivated account is correctly refused at web login, its existing API token continues to authenticate and to grant read and write access to the REST API (assets, users, licenses, etc.) at the account's prior permission level until the token expires. A deactivated account that retains user-management permissions can re-activate itself through the API, permanently defeating the deactivation control.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Snipeitapp Snipe-It.

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

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

## Is CVE-2026-86762 being exploited?

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

What it is: CVE-2026-86762 is a high-severity authentication bypass vulnerability in Snipeitapp Snipe-It, published on 9 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-86762 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-86762/ (Markdown: https://insights.sbomify.com/CVE-2026-86762/index.md)
```

## Sources

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

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