Skip to main content
VulnerabilityPublished

CVE-2026-37709: Snipe-IT has insecure permissions in file uploads

Affects snipe/snipe-itSource GCVE Database

0
Authoritative record:CVE-2026-37709· Critical 9.8

Not known to be exploited · CVSS 9.8 Critical : upgrade to 8.4.1 as a priority.

Data as of 27 Oct 2026, 00:07 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 8.4.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade snipe/snipe-it to 8.4.1.

Affected software

ProductAffectedFixed in
Packagistsnipe/snipe-itAffected
  • <8.4.1
Fixed in
  • 8.4.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

Insecure Permissions vulnerability in grokability snipe-it versions through 8.4.0, fixed after 2026-03-10 commit 676a9958, allow a remote attacker to execute arbitrary code via the `app/Http/Controllers/Api/UploadedFilesController.php` component ### Impact Users who can view assets, consumables, etc were able to send a POST request to `/api/v1/{object_type}/{id}/files`. The API authorized with "view" instead of write permission and persists the file and audit log entry. ### Patches Fixed after 2026-03-10 commit 676a9958, fix released to 8.4.1. ### Workarounds None.

References

Community reviews

Loading reviews…