Categories
CVE-2026-48507 high CVSS 7.1

Authorization Flaw in snipe/snipe-it (CVE-2026-48507)

Summary

Vulnerability in snipe/snipe-it (CVE-2026-48507). Risk of unauthorized operations or information disclosure. Exploitable via users.edit. Mitigation: upgrade to 8.6.0 or later.

Original description

The description as published by the source.

Snipe-IT is an IT asset/license management system. A vulnerability in versions prior to 8.6.0 allows a non-admin user holding only the granular users.edit permission to lock every admin out of the instance by editing the activated flag (which determines whether or not a user can login) and the ldap_import flag, which determines whether or not the user can request a password reset. Version 8.6.0 contains a patch.

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-48507 has been found in snipe/snipe-it.
Attackers can target a specific entry point like users.edit over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.1/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-48507" on the vendor's site.

CVE-2026-48507 (snipe/snipe-it) — CWE-863 / CVSS v3 7.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: users.edit / activated / ldap_import
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

Incorrect authorization (CWE-863) exists in snipe/snipe-it. Attackers reach the vulnerable code path via users.edit.

📍 Affected scope

Check the vendor advisory for the affected versions of snipe/snipe-it. Attack surface: users.edit / activated / ldap_import.

🔥 Severity

Severity: High (CVSS 7.1/10). Risk of unauthorized operations or information disclosure.

🔧 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 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.0

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

  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.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