Skip to main content
VulnerabilityPublished

CVE-2026-55694: grokability snipe-it · Insecure Direct Object Reference

Affects grokability snipe-itSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 8.6.3 soon.

Data as of 16 Nov 2026, 20:25 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Aug 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 16 Nov 2026.

What to do

Upgrade snipe-it and grokability/snipe-it to 8.6.3.

Affected software

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

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

AI-suggested

Upgrade Snipe-IT to version 8.6.3 or later, where this authorization bypass vulnerability is fixed. There is no official vendor advisory provided here, but the description explicitly states the issue is resolved in 8.6.3. Until upgrading, restrict access to the affected API endpoints and monitor for unauthorized access attempts if possible.

Description

Snipe-IT is an IT asset/license management system. Prior to 8.6.3, a restricted user can request /api/v1/users/{target_id}/eulas to obtain another user's randomized EULA filename and then download the signed file through /account/stored-eula-file/{filename}. The primary /stored-eula-file/{filename} route correctly denies access, but app/Http/Controllers/ProfileController.php and app/Http/Controllers/Api/UsersController.php do not consistently enforce ownership and target-user authorization. This issue is fixed in version 8.6.3.

References

Community reviews

Loading reviews…