Categories
CVE-2026-55466 high CVSS 8.7

Cross-Site Scripting (XSS) in snipe/snipe-it (CVE-2026-55466)

Summary

Cross-site scripting in snipe/snipe-it (CVE-2026-55466). Confidential information can be exposed externally. Exploitable via mimes. Mitigation: upgrade to 8.6.2 or later.

Original description

The description as published by the source.

Snipe-IT is an IT asset/license management system. Prior to 8.6.2, UploadFileRequest sanitizes SVG content only when PHP finfo reports image/svg+xml and UploadedFilesController serves attachments inline without using StorageHelper::allowSafeInline(), allowing a low-privilege user to upload active XHTML or XML content that is later served same-origin and executes JavaScript in a viewer’s browser. This issue is fixed in version 8.6.2.

Source: NIST National Vulnerability Database 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-55466 has been found in snipe/snipe-it.
Attackers can target a specific entry point like mimes over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.7/10.
What to do: upgrade snipe/snipe-it to 8.6.2 or later.
If unsure, ask your IT team or search "snipe/snipe-it CVE-2026-55466" on the vendor's site.

CVE-2026-55466 (snipe/snipe-it) — CWE-79 / CVSS v3 8.7
Attack vector: remote (network-reachable)
Attack surface: mimes / assets.view / assets.files / document.cookie
Patched: 8.6.2 — 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.

❓ What is the problem

Cross-site scripting (XSS) (CWE-79) exists in snipe/snipe-it. Attackers reach the vulnerable code path via mimes.

📍 Affected scope

Check the vendor advisory for the affected versions of snipe/snipe-it. Attack surface: mimes / assets.view / assets.files / document.cookie.

🔥 Severity

Severity: High (CVSS 8.7/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 8.6.2.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

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

  1. 1
    Identify exposure identify
    grep -r 'snipe/snipe-it' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で snipe/snipe-it を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade snipe/snipe-it to 8.6.2

    ステージング環境で 8.6.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

composer snipe/snipe-it
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.6.2"}]}]
Packagist snipe/snipe-it
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.6.2"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details