Open Redirect in Laravel Snipe-IT (CVE-2026-86756)
Summary
Vulnerability in Laravel Snipe-IT (CVE-2026-86756). Risk of unauthorized operations or information disclosure. Exploitable via POST /saml/acs. Mitigation: upgrade to 8.7.0 or later.
Original description
The description as published by the source.
Snipe-IT 8.5.0 through 8.6.3 contains an open redirect vulnerability in its SAML assertion-consumer endpoint (SamlController::acs, POST /saml/acs). The endpoint wrote the RelayState POST parameter directly into Laravel's url.intended session key with only CR/LF characters stripped, and LoginController later issued redirect()->intended(), which passes an absolute URL through to the Location header unchanged. An unauthenticated attacker who induces a user of a SAML-SSO-enabled instance to visit a crafted IdP-initiated SSO link can therefore cause the victim's browser to be redirected to an arbitrary absolute external URL immediately after a successful authentication, which the advisory notes facilitates credential-harvesting phishing. No account on the target instance and no compromise of the identity provider are required. Only deployments with SAML SSO enabled are affected. Fixed in 8.7.0 (commit d30b73d, PR #19386), which validates RelayState via a new Helper::sameOriginUrl check before storing it.
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-86756 has been found in Laravel Snipe-IT.
Attackers can target a specific entry point like POST /saml/acs over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.1/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-86756" on the vendor's site.
CVE-2026-86756 (Laravel Snipe-IT) — CWE-601 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: POST /saml/acs
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.
A vulnerability (CWE-601) exists in Laravel Snipe-IT. Attackers reach the vulnerable code path via POST /saml/acs without authentication.
Check the vendor advisory for the affected versions of Laravel Snipe-IT. Attack surface: POST /saml/acs.
Severity: Medium (CVSS 6.1/10). Risk of unauthorized operations or information disclosure.
Update to 8.7.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /saml/acs 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
-
1Identify exposure identify
grep -r 'Snipe-IT' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Snipe-ITを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /saml/acs' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /saml/acsへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade Laravel Snipe-IT to 8.7.0ステージング環境で 8.7.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /saml/acs on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- web github.com
- web vulncheck.com
- web nvd.nist.gov
- web github.com