Medium Logic error exploit reference

CVE-2026-86749 — snipe-it before 8.7.0 Data Loss via Failed Image Write

Snipe-IT versions <= 8.6.3 (fixed in 8.7.0) do not check the return value of storage write operations in ImageUploadRequest::handleImages(). Because Laravel's default disk mode does not throw on failure, a silently failed Storage::disk('public')->put(...) call still caused the application to delete the previous image via deleteExistingImage() and to reassign and persist the model's image reference to the new filename, destroying the existing image and leaving the database row pointing at a file that was never written. A mirror problem existed in deleteExistingImage(), where a failed Storage::delete() still nulled the model's image field, orphaning the file on disk. The condition is not directly attacker-controlled: it is triggered when any legitimate authenticated user submits an image upload while the storage backend transiently fails (for example an S3 network error, a local filesystem permission problem, or quota exhaustion). The result is unrecoverable loss of the prior image and a durable inconsistency between the database and disk that requires manual reconciliation. All models whose controllers route through ImageUploadRequest::handleImages (assets, asset models, users, companies, manufacturers, locations, categories, suppliers, departments, and other image-carrying models) are affected.

Published Sep 9, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: VulnCheck

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.3% (30-day exploitation probability)+4
Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.34%

ahead of 26% of scored CVEs · Oct 15, 2026

Affects

Grokability

Snipe-it

CVSS base

6.3

Medium · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

Documented patch — github.com (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Grokability Snipe-it, Snipeitapp Snipe-it).
Apply the fixed version or the patch documented under Remediation.
Exploitation requires user interaction: tighten email/web filtering and warn affected users.
Search available logs for exploit probes matching the vulnerability class (logic error), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Grokability	Snipe-it	< 8.7.0	Vulnerable	CVE Program (cve.org) e CISA ADP
Snipeitapp	Snipe-it	< 8.7.0	Vulnerable	NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

Low

User interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

Low

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
7.0	CVSS 4.0	High	—	—	disclosure@vulncheck.com via NIST National Vulnerability Database
7.0	CVSS 4.0	High	—	—	VulnCheck via CVE Program (cve.org) e CISA ADP
6.3	CVSS 3.1	Medium	2.1	4.2	disclosure@vulncheck.com via NIST National Vulnerability Database
6.3	CVSS 3.1	Medium	—	—	VulnCheck via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:L (score shown at the top: disclosure@vulncheck.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-252 · Unchecked Return Value

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).

web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

2026
Affected products added · grokability/snipe-it
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 15, 2026
Fix documented
Oct 15, 2026 · NIST National Vulnerability Database
CVSS changed · 6.3
Oct 15, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 15, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 15, 2026 · NIST National Vulnerability Database
CVE published
Sep 9, 2026 · VulnCheck

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

2 on the record

github.com/grokability/snipe-it/security/advisories/GHSA-v37p-hr9x-5w85
Exploit, Mitigation, Patch, Vendor Advisory, vendor-advisory, NIST National Vulnerability Database
www.vulncheck.com/advisories/snipe-it-before-8.7.0-data-loss-via-failed-image-write
Third Party Advisory, third-party-advisory, NIST National Vulnerability Database

Elsewhere on this site

Grokability
every CVE for this vendor

Logic error
same class

CWE-252
other pages naming this weakness

Related CVEs (same products)

Medium CVE-2026-63498 Snipe-IT: Stored XSS via Inline XML Rendering in the Uploaded Files API 21d
High CVE-2026-62368 Snipe-IT: Stored XSS via Custom Field name in asset-list column headers 21d
High CVE-2026-63493 Snipe-IT: 2FA bypass via the API token flow 21d
Medium CVE-2026-88894 Snipe-IT before 8.7.2 Authorization Bypass via Predefined Kit Checkout Sep 10, 2026
Medium CVE-2026-86773 Snipe-IT 8.6.3 Broken Access Control via Kit Update Endpoints Sep 9, 2026
Medium CVE-2026-86774 Snipe-IT before 8.7.0 Broken Access Control via AssetModelPolicy Sep 9, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-86749 is "snipe-it before 8.7.0 Data Loss via Failed Image Write", rated Medium. It affects Snipe-it (Grokability); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.3 describes technical severity. EPSS 0.34% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.