Skip to content
OpenAdvisories
High WID-SEC-2026-1918 4 CVEs

Snipe-IT: Mehrere Schwachstellen

Published Jun 14, 2026 · Updated Aug 19, 2026 · Revision 4 · de-DE

Summary

Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Snipe-IT ausnutzen, um administrative Berechtigungen zu erlangen, Sicherheitsmaßnahmen zu umgehen und Daten zu manipulieren.

Product

Snipe-IT ist eine webbasierte Open-Source-Asset-Management-Software, die Unternehmen bei der Verfolgung von Hardware und Software unterstützt.

Vulnerabilities 4

  • Medium 6.3

    Snipe-IT: Multi-Tenancy Bypass via Bulk Asset Update

    Snipe-IT is an IT asset/license management system. Prior to 8.4.1, a non-superadmin can use app/Http/Controllers/Assets/BulkAssetsController.php update() to submit company_id directly without Company::getIdForCurrentUser(), allowing assets to be moved across …

  • Medium 5.4

    Snipe-IT: Improper Authorization in File Deletion (IDOR)

    Snipe-IT is an IT asset/license management system. Prior to 8.4.1, an authenticated user with generic asset edit permission can delete files attached to assets outside the user's ownership or company assignment. The destroy() methods in app/Http/Controllers/A…

  • Medium 4.9

    Snipe-IT: Privilege Escalation via Missing admin Permission Check in User Creation

    Snipe-IT is an IT asset/license management system. Prior to 8.6.0, an authenticated user with users.create permission can submit the admin permission while creating a user because store() in app/Http/Controllers/Users/UsersController.php strips superuser perm…

  • Low 1.3

    Snipe-IT's S3 signature image retrieval lacks authorization before temporary URL

    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…

Revision history

  1. #4

    Referenz(en) aufgenommen: EUVD-2026-62681, EUVD-2026-62680, EUVD-2026-62679

  2. #3

    Referenz(en) aufgenommen: EUVD-2026-42398

  3. #2

    CVE ergänzt

  4. #1

    Initiale Fassung

References