Categories
CVE-2026-55694 medium CVSS 6.5

Vulnerability in snipe/snipe-it (CVE-2026-55694)

Summary

Vulnerability in snipe/snipe-it (CVE-2026-55694). Confidential information can be exposed externally. Exploitable via GET /stored-eula-file/{filename}. Mitigation: upgrade to 8.6.3 or later.

Original description

The description as published by the source.

Impact

An attacker can completely bypass file-name randomization security and without authorization download confidential, signed EULA files belonging to any other user across the application.

Steps to Reproduce:

  1. Log in as a restricted user.
  2. Send a GET request to /api/v1/users/{target_id}/eulas (where target_id belongs to a restricted/denied user).
  3. Observe the response leaks the secret EULA filename (e.g., eula-xxx.pdf).
  4. Attempt to access this file via the main route: GET /stored-eula-file/{filename} (This will correctly return 403 Forbidden).
  5. Now, access the file via the vulnerable profile route: GET /account/stored-eula-file/{filename}.
  6. Observe that the server returns a 200 OK and successfully downloads the target user's secret EULA file.

Patches

Fixed in https://github.com/grokability/snipe-it/commit/f15d78621b003be30ac114ba68626683894935ef

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-55694 has been found in snipe/snipe-it.
Attackers can target a specific entry point like GET /stored-eula-file/{filename} over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade snipe/snipe-it to 8.6.3 or later.
If unsure, ask your IT team or search "snipe/snipe-it CVE-2026-55694" on the vendor's site.

CVE-2026-55694 (snipe/snipe-it) — CWE-639 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /stored-eula-file/{filename} / GET /account/stored-eula-file/{filename}.
Patched: 8.6.3 — 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

A vulnerability (CWE-639) exists in snipe/snipe-it. Attackers reach the vulnerable code path via GET /stored-eula-file/{filename}.

📍 Affected scope

Check the vendor advisory for the affected versions of snipe/snipe-it. Attack surface: GET /stored-eula-file/{filename} / GET /account/stored-eula-file/{filename}..

🔥 Severity

Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 8.6.3.

🛡️ 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 GET /stored-eula-file/{filename} requests with malformed payloads or SQL meta-characters. 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
    Hunt for indicators of compromise detect
    grep 'GET /stored-eula-file/{filename}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /stored-eula-file/{filename} への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch
    Upgrade snipe/snipe-it to 8.6.3

    ステージング環境で 8.6.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify
    Replay attack against GET /stored-eula-file/{filename} on staging to confirm patch closes the vector

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

Affected packages

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

References

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