# CVE-2026-86747: snipe-it before 8.7.0 Authorization Bypass via Pivot-Only User > Authenticated users can delete acceptance records and view cross-company data in Snipe-IT when Full Multiple Company Support is enabled. - **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/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-3p87-695w-wwch, GHSA-p5wx-p3vv-g6p2 ## What is CVE-2026-86747? CVE-2026-86747 is a medium-severity missing authorization 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 is an open source IT asset management system. In versions up to and including 8.6.3, the report acceptance endpoints POST /reports/unaccepted_assets/sent_reminder (ReportsController::sentAssetAcceptanceReminder) and DELETE /reports/unaccepted_assets/{acceptanceId}/delete (ReportsController::deleteAssetAcceptance) are not correctly scoped when Full Multiple Company Support (FMCS) is enabled. In 8.6.3 the guard ReportsController::currentUserCanAccessAcceptance() early-exits with 'return true' when '! $user->company_id' is truthy, which is the case for every pivot-only user (a user associated with companies through the company_user pivot table whose scalar users.company_id column is NULL); versions prior to 8.6.3 lacked the guard altogether. As a result, an authenticated user holding the reports.view permission can send acceptance-reminder emails for, and permanently delete, any pending acceptance record in the install regardless of which company owns the underlying checkoutable. Deletion is destructive and forfeits the acceptance audit trail for the affected item, and the reminder email exposes limited cross-company acceptance context (item name and assignment metadata) to the recipient. Acceptance IDs are sequential integers and can be enumerated. This issue is fixed in version 8.7.0. Weakness: CWE-863 (Incorrect Authorization) ## Which versions are affected by CVE-2026-86747? It affects 1 product. Products: Snipeitapp Snipe-It. ## How do I fix CVE-2026-86747? No fix has been published for CVE-2026-86747 yet. Limit exposure of the affected software until one is available. ## Is CVE-2026-86747 being exploited? There is no known exploitation of CVE-2026-86747 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-86747 and fix it if it is affected. What it is: CVE-2026-86747 is a medium-severity missing authorization 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-86747 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-86747/ (Markdown: https://insights.sbomify.com/CVE-2026-86747/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-86747 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-86747 - OSV: https://osv.dev/vulnerability/CVE-2026-86747 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-86747/ Summaries are generated and may contain mistakes; the official description above is the record.