Categories
CVE-2026-86755 medium CVSS 5.4

Authorization Flaw in Laravel Snipe-IT (CVE-2026-86755)

Summary

Vulnerability in Laravel Snipe-IT (CVE-2026-86755). Risk of unauthorized operations or information disclosure. Exploitable via DELETE /oauth/personal-access-tokens. Mitigation: upgrade to 8.7.0 or later.

Original description

The description as published by the source.

Snipe-IT versions 4.2.0 through 8.6.3 expose Laravel Passport's auto-registered personal-access-token routes (GET, POST, DELETE /oauth/personal-access-tokens*) with only 'web' and 'auth:web' middleware, without the self.api permission gate that Snipe-IT enforces on its own token endpoints (/account/api and /api/v1/account/personal-access-tokens). Any user with a valid web session and the corresponding CSRF token can POST to /oauth/personal-access-tokens and mint a long-lived bearer token for their own account, even when an administrator has denied the self.api permission. The issued token is still subject to existing per-endpoint authorization policies, so this is not a privilege escalation; it defeats the administrative control intended to block API/scripted access at the user's own permission level. Fixed in 8.7.0 (commit 3f74b8c), which registers overriding routes wrapped in the can:self.api middleware.

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-86755 has been found in Laravel Snipe-IT.
Attackers can target a specific entry point like DELETE /oauth/personal-access-tokens over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade Laravel Snipe-IT to 8.7.0 or later.
If unsure, ask your IT team or search "Laravel Snipe-IT CVE-2026-86755" on the vendor's site.

CVE-2026-86755 (Laravel Snipe-IT) — CWE-863 / CVSS v3 5.4
Attack vector: remote (network-reachable) / no user interaction
Attack surface: DELETE /oauth/personal-access-tokens
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

Incorrect authorization (CWE-863) exists in Laravel Snipe-IT. Attackers reach the vulnerable code path via DELETE /oauth/personal-access-tokens.

📍 Affected scope

Check the vendor advisory for the affected versions of Laravel Snipe-IT. Attack surface: DELETE /oauth/personal-access-tokens.

🔥 Severity

Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.

🔧 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 DELETE /oauth/personal-access-tokens requests with malformed payloads or SQL meta-characters. Run grep -r '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-IT' . | grep -v node_modules

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

  2. 2
    Hunt for indicators of compromise detect
    grep 'DELETE /oauth/personal-access-tokens' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

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

  3. 3
    Apply patch patch
    Upgrade Laravel Snipe-IT to 8.7.0

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

  4. 4
    Post-deployment verification verify
    Replay attack against DELETE /oauth/personal-access-tokens on staging to confirm patch closes the vector

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

References

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