Skip to main content

Snipe-IT CVE-2026-55515

| EUVDEUVD-2026-42995 MEDIUM
Authorization Bypass Through User-Controlled Key (CWE-639)
2026-07-10 security-advisories@github.com GHSA-35cr-9hqq-p2mg
5.0
CVSS 3.1 · Vendor: github
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain reports.view account in any tenant
  2. Delivery
    Enumerate global CheckoutAcceptance IDs via delete endpoint
  3. Exploit
    Submit DELETE requests with cross-company IDs
  4. Execution
    Endpoint validates reports.view role only
  5. Impact
    Cross-tenant records deleted successfully

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
Exploitation Conditions

Exploitation requires an authenticated user account assigned the reports.view permission in any company on the Snipe-IT instance - this is confirmed by the CVSS vector (PR:L) and the advisory description. The instance must be configured with multiple companies (multi-tenant deployment); single-company deployments are not meaningfully affected. The attacker must be able to reach the Snipe-IT web interface over the network (AV:N). ID enumeration is the only technical prerequisite, as Snipe-IT likely uses sequential integer primary keys. Exploitation is limited by: (1) requiring a valid authenticated session with at minimum reports.view access, (2) being scoped only to deleting pending CheckoutAcceptance records - read access to cross-company data or modification of asset records is not enabled by this flaw, and (3) having no impact on single-tenant instances where company isolation is not in use.

Impact

The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N = 5.0) is consistent with the vulnerability description: network-accessible, low complexity, requiring only a low-privileged reports.view account, with scope change reflecting cross-tenant impact. The moderate 5.0 score appropriately reflects the bounded integrity-only impact - no data is exposed (C:N) and bulk availability is unaffected (A:N). The scope change (S:C) is the most significant signal: it indicates the blast radius extends beyond the attacker's own tenant, which is a serious concern for shared-instance deployments. No EPSS data was provided in the input; exploitation probability cannot be quantified from available signals. This CVE is not in the CISA KEV catalog, and no POC is known, so active exploitation is not confirmed. Real-world risk is elevated specifically for multi-company Snipe-IT deployments; single-tenant instances are not meaningfully affected since all users already share the same company context.

Exploit ScenarioDerived

An attacker with a reports.view account in Company A iterates sequential integer IDs against the unaccepted-assets report delete endpoint, targeting CheckoutAcceptance records whose IDs fall outside their own company's range. Because the endpoint only verifies the reports.view role and not company membership, deletion succeeds for records owned by Company B or any other tenant on the instance. The attacker systematically erases Company B's pending asset checkout approvals, disrupting their IT asset onboarding workflow. No public exploit code has been identified at time of analysis.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 10, 2026

Cross-tenant authorization bypass in Snipe-IT prior to v8.6.2 allows an authenticated user with only reports.view permission in one company to delete pending checkout acceptance records belonging to any other company by supplying arbitrary global IDs to the unaccepted-assets report delete endpoint. The root cause is a classic IDOR (CWE-639): the endpoint validates role but not company-scope ownership. No public exploit has been identified and this CVE is absent from the CISA KEV catalog, but multi-tenant deployments relying on organizational data isolation are directly impacted.

RemediationAI

Upgrade to Snipe-IT v8.6.2 or later, which introduces company-scope validation on the unaccepted-assets delete endpoint. The patching commit is 802067f3987a4b65bfc2efe60e22e07c24e01e6a (https://github.com/grokability/snipe-it/commit/802067f3987a4b65bfc2efe60e22e07c24e01e6a) and the release is at https://github.com/grokability/snipe-it/releases/tag/v8.6.2. If immediate patching is not feasible for a multi-company instance, revoke or restrict the reports.view permission from user accounts that belong to a company that should not interact with other tenants' data - this reduces the pool of accounts that could be misused, though it may limit legitimate reporting workflows. Alternatively, restrict network access to the Snipe-IT admin interface to trusted internal segments via firewall rules, reducing the exposure to users already on the internal network; note this does not eliminate insider risk. There is no documented vendor-supported workaround other than upgrading to v8.6.2.

Affected VersionsENISA

snipe-it < 8.6.2

Affected Packages

composer snipe/snipe-it fix: 8.6.2
euvd snipe_it fix: 8.6.2

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in composer, euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Snipe-IT is an open-source PHP/Laravel IT asset and license management system supporting multi-company (multi-tenant) deployments where distinct organizations share one instance with isolated data. The vulnerable endpoint handles deletion of CheckoutAcceptance records - database rows representing pending approvals for asset checkouts. The delete handler resolves records via CheckoutAcceptance::pending()->find($acceptanceId) using a globally scoped ORM query, then authorizes the action by checking only the reports.view permission without asserting that the acceptance record's related checkoutable asset belongs to the requesting user's company. CWE-639 (Authorization Bypass Through User-Controlled Key) precisely describes this flaw: the application trusts a user-supplied integer ID to identify a resource without enforcing ownership or tenancy boundaries. Because database primary keys are typically sequential integers, enumeration is trivially feasible.

Know when Snipe It gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (github) PRIMARY 5.0 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N
vuln.today AI 5.0 MEDIUM

PR:L confirmed by required reports.view role; S:C reflects cross-tenant record deletion; I:L only since impact is confined to deleting acceptance records with no confidentiality or availability consequences.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N

Primary rating from Vendor (github).

CVSS VectorVendor: github

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
None
Integrity
Low
Availability
None

Lifecycle Timeline

1
Patch available
Jul 10, 2026 - 21:02 EUVD

DescriptionCVE.org

Snipe-IT is an IT asset/license management system. Prior to 8.6.2, the unaccepted-assets report delete endpoint authorizes only reports.view and deletes CheckoutAcceptance::pending()->find($acceptanceId) by global ID without checking access to the related checkoutable asset, allowing a reports user in one company to delete pending checkout acceptance records for another company. This issue is fixed in version 8.6.2.

Threat Intelligence Overview

EPSS Score
0.2%
Top 84% exploitable
Prevalence
Low
niche open-source IT asset management tool, limited enterprise footprint
Threat Intel
1
1 sources
Exploit
POC
Public exploit code exists
Data Quality
6 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GHSA GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

45
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +25
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

CVE-2023-5511 HIGH POC
8.8 Oct 11

Cross-Site Request Forgery (CSRF) in GitHub repository snipe/snipe-it prior to v.6.2.3. Rated high severity (CVSS 8.8),

CVE-2022-23064 HIGH POC
8.8 May 02

In Snipe-IT, versions v3.0-alpha to v5.3.7 are vulnerable to Host Header Injection. Rated high severity (CVSS 8.8), this

CVE-2021-4130 HIGH POC
8.8 Dec 18

snipe-it is vulnerable to Cross-Site Request Forgery (CSRF). Rated high severity (CVSS 8.8), this vulnerability is remot

CVE-2021-3858 HIGH POC
8.8 Oct 19

snipe-it is vulnerable to Cross-Site Request Forgery (CSRF). Rated high severity (CVSS 8.8), this vulnerability is remot

CVE-2026-63493 HIGH POC
8.6 Sep 24

Two-factor authentication bypass in Snipe-IT (all releases before 8.7.0) allows an attacker who already knows a victim's

CVE-2022-2997 HIGH POC
8.0 Aug 25

Session Fixation in GitHub repository snipe/snipe-it prior to 6.0.10. Rated high severity (CVSS 8.0), this vulnerability

CVE-2022-1155 HIGH POC
7.4 Mar 30

Old sessions are not blocked by the login enable function. Rated high severity (CVSS 7.4), this vulnerability is remotel

CVE-2021-4075 HIGH POC
7.2 Dec 06

snipe-it is vulnerable to Server-Side Request Forgery (SSRF). Rated high severity (CVSS 7.2), this vulnerability is remo

CVE-2026-55460 HIGH POC
7.1 Jul 10

Broken authorization in Snipe-IT before 8.6.2 lets an authenticated non-admin user who holds users.view and users.edit -

CVE-2026-48507 HIGH POC
7.1 Jun 08

Privilege escalation via authorization bypass in Snipe-IT versions prior to 8.6.0 allows any authenticated user holding

CVE-2026-55843 HIGH POC
7.0 Jul 10

Improper permission handling in Snipe-IT before 8.6.0 lets a privileged user strip another user's administrative or gran

CVE-2024-48987 MEDIUM POC
6.6 Oct 11

Snipe-IT before 7.0.10 allows remote code execution (associated with cookie serialization) when an attacker knows the AP

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy