Skip to main content
VulnerabilityPublished

CVE-2026-55542: grokability snipe-it · Missing Authorization

Affects grokability snipe-itSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 1.3 Low : upgrade to 8.5.1 when convenient.

Data as of 21 Nov 2026, 17:35 UTC

CVSS 4.0 base score
1.3Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 8.5.1, 8.6.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:U

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 21 Nov 2026.

What to do

Upgrade snipe-it to 8.5.1; grokability/snipe-it to 8.6.1.

Affected software

ProductAffectedFixed in
grokabilitysnipe-itAffected
  • <8.5.1
Fixed in
  • 8.5.1
GitHubgrokability/snipe-itpkg:github/grokability/snipe-itOther threatsAffected
  • <8.6.1
Fixed in
  • 8.6.1

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

AI-suggested

A patch is available in Snipe-IT version 8.6.1 that fixes the missing authorization check. Since this is a cloud-hosted service, the vendor manages remediation for the cloud environment. Users should upgrade to version 8.6.1 or later to ensure the vulnerability is addressed.

Description

Snipe-IT is an IT asset/license management system. Prior to version 8.6.1, Snipe-IT S3 signature image retrieval lacks authorization before temporary URL. On S3-backed deployments, authenticated users who know a signature filename can obtain a 5-minute signed S3 URL because the S3 branch returns before the `authorize()` call used by the local-file branch. Version 8.6.1 contains a patch.

References

Community reviews

Loading reviews…