Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-63493 high CVSS 8.1

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

Summary

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

Original description

The description as published by the source.

Impact

An attacker who knows a victim's password fully bypasses that account's 2FA and obtains a persistent token with full API access as the user (read and write across the user's permissions, including admin if the victim is an admin).

The token is an API credential, not a web/UI session (using it on web routes redirects to /login), but the REST API covers essentially the whole application. If the victim is an admin, the token can also call the admin users/two_factor_reset endpoint, which is in the same un-gated API surface, to clear the account's enrolled 2FA. The next login is then forced to re-enroll a second factor, which the password-holding attacker can complete with their own device, taking over the account's web access and locking the legitimate user out.

Summary:

2FA is enforced only by the web middleware group, not the api group, and the personal-access-token endpoint is in the api group. A session that has passed the password check but not the 2FA can mint a persistent API token and use it for full API access.

Details:

CheckForTwoFactor is in the web group but not the api group:

// app/Http/Kernel.php
'web' => [ ..., CheckForTwoFactor::class, CreateFreshApiToken::class, ... ],
'api' => [ 'auth:api', EnforceApiUserAgent::class, ... ],   // no CheckForTwoFactor

Two consequences:

  1. /two-factor is exempt from the check, and CreateFreshApiToken runs right after it in the web group:

    // app/Http/Middleware/Chec…

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

CVE-2026-63493 (snipe/snipe-it) — CWE-288 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /two-factor / GET /api/v1/users / web / api
Patched: 8.7.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-288) exists in snipe/snipe-it. Attackers reach the vulnerable code path via GET /two-factor.

📍 Affected scope

Check the vendor advisory for the affected versions of snipe/snipe-it. Attack surface: GET /two-factor / GET /api/v1/users / web / api.

🔥 Severity

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

🔧 How to fix

Update to 8.7.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 GET /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 'GET /two-factor' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

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

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

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

  4. 4
    Post-deployment verification verify 
    Replay attack against GET /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.7.0"}]}]

References

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