# CVE-2026-86739: Snipe-IT before 8.7.0 Acceptance Finalization Without Stored Evidence

> Authenticated users can finalize asset acceptances without storing evidence files if the storage backend fails silently, creating incomplete compliance records.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/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:** 18 Sep 2026
- **Also known as:** GHSA-h543-58f9-v6mj, GHSA-pgrg-wpfj-73cq

## What is CVE-2026-86739?

CVE-2026-86739 is a low-severity 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 8.6.3 and earlier do not check the return value of Storage::put() when writing the signature PNG and the generated acceptance PDF in Account\AcceptanceController::store(). On filesystem drivers that return false instead of throwing on a write failure (for example the local disk with restrictive permissions, S3 with expired credentials, or a storage backend that is out of quota), execution continues into $acceptance->accept(), which sets accepted_at and the signature_filename/eula_filename fields, creates the 'accepted' action-log entry, and dispatches completion notifications even though the evidence files were never stored. The result is an acceptance record marked complete whose supporting evidence files do not exist, yielding a materially incomplete compliance artifact for EULA acknowledgement or equipment-receipt workflows. The condition is triggered when an authenticated user completes an acceptance while the storage backend is silently failing writes; an attacker cannot directly force the storage backend into that state. Fixed in Snipe-IT 8.7.0.

Weakness: CWE-252 (Unchecked Return Value)

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

It affects 1 product.


Products: Snipeitapp Snipe-It.

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

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

## Is CVE-2026-86739 being exploited?

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

What it is: CVE-2026-86739 is a low-severity 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-86739 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-86739/ (Markdown: https://insights.sbomify.com/CVE-2026-86739/index.md)
```

## Sources

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

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