llamaCVEVulnerability Intelligence
/
snipe-it

CVE-2026-86749

snipe-it before 8.7.0 Data Loss via Failed Image Write

Specific setups onlyParche disponibleunchecked return value
Descargar PNG JSON
CVSS 4.0
7.0
Alta
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N Fuente: CNA
ExplotaciónSin evidenciaSSVC: none · no figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche1 versión8.7.0
Exposición71 dDesde la divulgación, 9 sept 2026, 8:32 a. m.
Detección68 dDesde la divulgación hasta su ingreso al índice
Decisión SSVCSeguir
Remediar en la ventana regular de mantenimiento
Sin explotación conocida, no automatizable e impacto técnico parcial. Hay versiones corregidas disponibles.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Evaluación SSVC
Modificada
Explotación
Remediación
Monitoreo
Detectada
Fuente: OSV +1
9 sept 26
18 sept 26
19 sept 26
17 nov 26
18 nov 26
19 nov 26
9 sept 26
27 sept 26
15 oct 26
1 nov 26
19 nov 26
FechaFaseEventoDetalle
Divulgación Publicada CVE-2026-86749 divulgada · CVSS 7 (CNA)
Divulgación Evaluación SSVC CISA-ADP · explotación ninguna
Divulgación Modificada Última actualización del registro
Monitoreo Detectada Ingresó al índice
Monitoreo Fuente: OSV Registro visto por primera vez en OSV
Monitoreo Verificada Última verificación contra las fuentes
Resumen

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.

Snipe-IT 8.6.3 and earlier can destroy an existing model image when a storage upload transiently fails. Fixed in 8.7.0.

¿Qué significa?When the storage backend transiently fails during an image upload, Snipe-IT does not check the write's return value. It destroys the existing image and leaves the database row pointing at a file that was never written, which requires manual reconciliation. A failed delete can also leave orphaned files on disk.
¿Quién está afectado?Snipe-IT versions up to and including 8.6.3 are affected, in setups using Laravel's default disk mode, which does not throw on write failure. A reader can check the installed version in the application and the storage disk configuration to see whether this setup applies.
¿Qué hacer?Upgrade Snipe-IT to 8.7.0 or later, which fixes the unchecked return value.
Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
Snipe-IT versions up to and including 8.6.3 (fixed in 8.7.0)“Snipe-IT versions <= 8.6.3 (fixed in 8.7.0) do not check the return value”
02
Storage backend transiently fails during an image upload (for example S3 network error, local permission problem, or quota exhaustion)“while the storage backend transiently fails”
03
Laravel default disk mode, which does not throw on write failure“Because Laravel's default disk mode does not throw on failure”
¿Quién debe revisar?Teams running Snipe-IT 8.6.3 or earlier that let users upload images for assets, asset models, users, companies, manufacturers, locations, categories, suppliers, departments, or other image-carrying models
Vector CVSS 4.0

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · CNA
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:L
BajaAlta
Requisitos de ataqueAT:N
NingunoPresentes
PrivilegiosPR:L
NingunoBajosAltos
InteracciónUI:P
NingunaPasivaActiva
Confid. (sistema)VC:N
AltoBajoNinguno
Integridad (sistema)VI:H
AltoBajoNinguno
Disponib. (sistema)VA:L
AltoBajoNinguno
Confid. (posterior)SC:N
AltoBajoNinguno
Integridad (posterior)SI:N
AltoBajoNinguno
Disponib. (posterior)SA:N
AltoBajoNinguno
Versiones

Rangos afectados

Afectada Corregida
snipe-it< 8.7.0
8.7.0
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
snipe-it
Corregida 8.7.0 — —
Versiones corregidas8.7.0
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Fabricantehttps://github.com/grokability/snipe-it/security/advisories/GHSA-v37p-hr9x-5w85
Otrahttps://www.vulncheck.com/advisories/snipe-it-before-8.7.0-data-loss-via-failed-image-write

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.