Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-49870 medium CVSS 5.9

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

Summary

Vulnerability in snipe/snipe-it (CVE-2026-49870). Confidential information can be exposed externally. Exploitable via POST /two-factor. Mitigation: upgrade to 8.6.0 or later.

Original description

The description as published by the source.

Impact

POST /two-factor had no rate limiting, lockout, or attempt counter. An attacker with valid credentials can submit unlimited TOTP guesses. The TOTP implementation accepts the current code plus one step on either side (config/google2fa.php window=1), so at any instant 3 of 1,000,000 codes are accepted.

After a correct guess the attacker holds a fully authenticated session. If the instance is configured with 2FA in optional mode (two_factor_enabled='1'), the attacker can additionally disable 2FA via POST /account/profile with two_factor_optin=0. No OTP re-verification is required. The account is then accessible with the password alone on future logins. If 2FA is in required-for-all mode (='2'), the per-user opt-out path is closed and the impact stops at session-level account takeover. For an admin target, POST /api/v1/users/two_factor_reset additionally clears another user's 2FA secret.

Patches

Patched in v8.6.0

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

CVE-2026-49870 (snipe/snipe-it) — CWE-770 / CVSS v3 5.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /two-factor / POST /account/profile / POST /api/v1/users/two_factor_reset
Patched: 8.6.0 — 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-770) exists in snipe/snipe-it. Attackers reach the vulnerable code path via POST /two-factor.

📍 Affected scope

Check the vendor advisory for the affected versions of snipe/snipe-it. Attack surface: POST /two-factor / POST /account/profile / POST /api/v1/users/two_factor_reset.

🔥 Severity

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

🔧 How to fix

Update to 8.6.0.

🛡️ 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 POST /two-factor 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 'POST /two-factor' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

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

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

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

  4. 4
    Post-deployment verification verify 
    Replay attack against POST /two-factor 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.0"}]}]
Packagist snipe/snipe-it
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.6.0"}]}]

References

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