Vulnerability in snipe/snipe-it (CVE-2026-55542)
Summary
Vulnerability in snipe/snipe-it (CVE-2026-55542). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 8.5.1 or later.
Original description
The description as published by the source.
Impact
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.
Key evidence
routes/web.php:135-143; app/Http/Controllers/ActionlogController.php:16-44; app/Http/Controllers/Account/AcceptanceController.php:160,175; app/Listeners/LogListener.php:56; app/Http/Transformers/ActionlogsTransformer.php:188
Patches
Patched in https://github.com/grokability/snipe-it/commit/ded6515cbc27a28f07395da318483c2e96263259
Credit
Disclosed by Ikaro tiagonas
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-55542 has been found in snipe/snipe-it.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade snipe/snipe-it to 8.5.1 or later.
If unsure, ask your IT team or search "snipe/snipe-it CVE-2026-55542" on the vendor's site.
CVE-2026-55542 (snipe/snipe-it) — CWE-862 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 8.5.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-862) exists in snipe/snipe-it.
Check the vendor advisory for the affected versions of snipe/snipe-it.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 8.5.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'snipe/snipe-it' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'snipe/snipe-it' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
snipe/snipe-itを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade snipe/snipe-it to 8.5.1ステージング環境で 8.5.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web github.com