Aug 20, 2026·5 min read·59 visits
An insecure direct object reference (IDOR) flaw in Snipe-IT allows any authenticated user to view asset maintenance logs and financial/vendor data without permission.
Snipe-IT is an IT asset/license management system. Prior to 8.6.3, any activated account can request /maintenances/{id} and read maintenance records for assets in the same company without asset or maintenance permission. app/Http/Controllers/MaintenancesController.php show() renders the record without authorize(), while company-scoped route-model binding only prevents access to other companies. Disclosed fields include asset tags, suppliers, purchase costs, notes, and dates. This issue is fixed in version 8.6.3.
Snipe-IT is an open-source IT asset management system designed for tracking licenses, accessories, consumables, and physical hardware assets. Within enterprise deployments, access control is critical to limit exposure of asset maintenance history, pricing, vendor relationships, and configuration notes. The vulnerability, designated as CVE-2026-55703, represents a Missing Function-Level Access Control (MFLAC) flaw in the application's maintenance reporting module.
Historically, physical assets and their subsequent maintenance operations require specific operator permissions to view or edit. However, an oversight in the endpoint handling maintenance details allowed low-privileged authenticated users to access sensitive data. This analysis details the underlying code flaw, exploitation path, and vendor remediation implemented in the patched version.
The root cause of CVE-2026-55703 resides in the show method of app/Http/Controllers/MaintenancesController.php. This controller handles operations related to asset maintenance, including scheduling, updates, and general logging. While other controller actions like edit, update, and destroy implement explicit validation logic or utilize Laravel authorization gates, the show method completely omitted these security boundaries.
Laravel uses route-model binding to automatically inject model instances based on URL parameters. For example, a request to /maintenances/123 binds the Maintenance model instance with ID 123 to the corresponding controller parameter. While Snipe-IT employs Multiple Company Support (FMCS) to restrict cross-tenant exposure, it does not enforce granular individual-user access permissions at the database-binding level within the same company scope.
Without an explicit authorization check, the application implicitly trusts the request from any authenticated user. The endpoint serves the requested maintenance view without verifying whether the requesting session possesses the necessary view rights for the associated hardware asset. This allows any active account to retrieve potentially sensitive records.
To understand the technical mechanism of the vulnerability, we analyze the implementation of MaintenancesController::show prior to the patch. The vulnerable method directly returned the view template populated with the bound Maintenance model instance.
// Vulnerable Code Path
public function show(Maintenance $maintenance): View|RedirectResponse
{
return view('maintenances.view')->with('maintenance', $maintenance);
}The lack of access control is resolved by adding an explicit authorization check that links back to the parent asset's visibility rights. The corrected method invokes Laravel's native policy engine prior to rendering the final view template.
// Patched Code Path (Commit 69c50aa2aee25f837626556b4f4f3d05ec7ace96)
public function show(Maintenance $maintenance): View|RedirectResponse
{
+ $this->authorize('view', $maintenance->asset);
+
return view('maintenances.view')->with('maintenance', $maintenance);
}This remediation ensures that if the authenticated session lacks the permission to view the specific hardware asset linked to the maintenance, Laravel throws an AuthorizationException. This exception is subsequently caught by the framework handler to return an HTTP 403 Forbidden response.
Exploitation of CVE-2026-55703 is straightforward and requires only basic authenticated access to the target Snipe-IT instance. Since the application does not validate individual permissions for the show method, an attacker can perform an Insecure Direct Object Reference (IDOR) attack to enumerate sequential maintenance IDs.
An attacker begins by logging into their low-privileged user account to obtain a valid session cookie or API bearer token. They then construct and transmit an HTTP GET request targeting the /maintenances/{id} endpoint, replacing {id} with sequential integers to harvest data.
GET /maintenances/415 HTTP/1.1
Host: target-snipeit.local
Authorization: Bearer <user_token>
Accept: text/html,application/xhtml+xmlThe server responds with HTTP 200 OK and returns the HTML layout for the requested maintenance record. The returned document leaks sensitive data points including vendor details, hardware identifiers, purchase costs, internal notes, and service dates.
The security impact of this vulnerability is characterized as a partial loss of confidentiality. Because the vulnerability allows users to read unauthorized maintenance records, attackers can gain exposure to internal asset details, proprietary workflows, and financial information associated with physical assets.
Specifically, the leaked data fields include asset tags, supplier names, purchase values, and detailed action notes. These details can be leveraged to perform further social engineering attacks, mapping out internal infrastructure, or gathering competitive intelligence on hardware spend.
This vulnerability holds a CVSS v3.1 base score of 4.3 (Medium). The attack complexity is low, and the privilege required is low. The impact remains confined to confidentiality, with no integrity or availability degradation possible through this single exploit vector.
The recommended mitigation is to upgrade Snipe-IT to version 8.6.3 or later. This version implements the proper authorization checks in the MaintenancesController and provides comprehensive test cases to prevent regressions.
For administrators unable to apply the update immediately, several temporary workarounds help lower risk. Restrict access to the Snipe-IT interface to a trusted virtual private network (VPN) and audit active user accounts to ensure only authorized personnel have active logins. Additionally, monitoring application logs for anomalous sequential access patterns on /maintenances/ paths helps identify potential enumeration attempts.
To detect potential exploitation retrospectively, security teams can inspect web server access logs. Repeated, sequential GET requests to /maintenances/ originating from a single user session or IP address are indicative of automated IDOR enumeration.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N| Attribute | Detail |
|---|---|
| CWE ID | CWE-862 |
| Attack Vector | Network (AV:N) |
| CVSS v3.1 Score | 4.3 (Medium) |
| Impact | Partial Confidentiality Loss |
| Exploit Status | No public PoC |
| KEV Status | Not Listed |
The application fails to perform an authorization check when an actor attempts to access a resource.
CVE-2026-9639 (GHSA-j93m-3j9p-m5m8) is a null pointer dereference vulnerability in Canonical LXD affecting versions 5.0.0 through 5.21.4 and 6.0 through 6.8. The flaw resides in the (*lxdBackend).CreateCustomVolumeFromBackup method within lxd/storage/backend_lxd.go. An authenticated attacker with the can_create_storage_volumes permission can upload a crafted custom volume backup tarball that omits the expires_at field on a snapshot entry, triggering an unhandled SIGSEGV panic and terminating the LXD daemon.
An operating system command injection vulnerability (CWE-78) exists in GeoNode versions prior to 5.1.0. The vulnerability occurs in the vector upload processing pipeline when handling user-supplied geospatial files. By supplying a crafted layer name containing shell metacharacters, an authenticated attacker with basic data upload privileges can execute arbitrary commands on the underlying server or container hosting the GeoNode application and Celery worker processes.
GeoNode versions prior to 5.0.3 contain an unrestricted file upload vulnerability (CWE-434) within the document and dataset ingestion architecture. Authenticated low-privileged users can bypass upload validation via direct REST API interactions, file extension masquerading, metadata mutation via PATCH requests, or malicious archive submissions. This allows attackers to store and serve dangerous file types, alter on-disk file references, or trigger path traversal and resource exhaustion during archive extraction.
CVE-2026-55649 is a stored Cross-Site Scripting (XSS) vulnerability in GeoNode versions prior to 5.0.3. The flaw exists because document abstract metadata fields are ingested via the metadata management pipeline and stored in the backend database without HTML sanitization or input neutralization. An authenticated attacker with privileges to create or edit document metadata can inject arbitrary HTML and JavaScript payloads into these fields. When another user, such as an administrator, views the affected document page or catalog listing, the unencoded payload is rendered into the Document Object Model (DOM) and executes within the victim's browser session.
CVE-2026-55622 (GHSA-qx75-2p3r-pwm5) is an improper access control vulnerability (CWE-284) in Canonical LXD and LXC Incus (tracked as GHSA-c9f5-j9c3-mhrg). In multi-tenant deployments utilizing project-based isolation, the REST API handler for instance creation via POST /1.0/instances verifies that the authenticated user has authorization in the destination project specified by the query parameter, but fails to verify whether the user holds read or view permissions for the source instance when executing a copy operation across projects. Consequently, an authenticated client restricted to a single project can clone instances or snapshots from unauthorized projects into their own project, resulting in complete disclosure of the target instance filesystem and embedded credentials.
An authorization bypass vulnerability in Canonical LXD (tracked as GHSA-7mr3-28h5-m5vx and CVE-2026-55621, and as GHSA-64f3-v33m-w89f in Linux Containers Incus) allows an authenticated user with restricted project access to copy custom storage volumes and volume snapshots from unauthorized projects. The flaw resides in the storagePoolVolumesPost REST API handler, which verifies permissions on the destination project but fails to check whether the caller holds view entitlements on the source project or volume specified in the request body.