All vulnerabilities

Servers and applications

CVE-2026-86756

Open redirect via unvalidated SAML RelayState parameter after successful IdP-initiated login

Severity
Medium 5.3
Published
24 Aug 2026
Last changed
16 Sept 2026
Added to UpHeron
3 Nov 2026
Fixed in
8.7.0
Exploit chance
0.3% in the next 30 daysHigher than 27% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Open redirect (CWE-601)
Attack
Over the network · No login needed · Needs someone to view a page or file
Attacker can
Read some data · Change some data
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Also known as
GHSA-68hq-m589-8q9j
Sources
NVD, Project advisories (GitHub)

Description

Snipe-IT's SAML assertion-consumer endpoint (SamlController::acs, POST /saml/acs) accepted the RelayState POST parameter from an incoming SAML response and wrote it directly into Laravel's url.intended session key with only a CR/LF strip applied:

After the SAML round-trip completed and the user was authenticated, three different consumers in LoginController (the logout post-auth redirect, authenticated, and showLoginForm) all called redirect()->intended('/') or redirect()->intended(). Laravel's Redirector::intended() passes an absolute URL through to the Location header unchanged, so an attacker-controlled absolute URL stored in url.intended was reflected verbatim as the redirect target.

The RelayState parameter is part of the SAML web browser SSO profile and is populated by the identity provider on IdP-initiated login. Any IdP that follows the profile will pass through a RelayState value it receives in the request, so an attacker who could send a victim a crafted IdP-initiated SSO…

From grokability/snipe-it's security advisory. Shortened; the full text is there.

Workarounds

Until the patch is applied, deployments that must run an affected version should disable SAML SSO in settings. There is no request-level workaround at the application layer, since the vulnerable path is reached through a legitimate SAML response and gets no chance to inspect the value before the redirect.

Workarounds as given by grokability/snipe-it's security advisory.

Affected software

SoftwareAffected versions
Snipe-ITServers and applications · cpe:a:snipeitapp:snipe-it
  • From 8.5.0 before 8.7.0
Snipe-ITServers and applications · github:grokability/snipe-it
  • From 8.5.0 before 8.7.0

About Snipe-IT

A free open source IT asset/license management system

From its GitHub repository.
Docker Hub pulls
29,869,543Docker Hub, 15 Nov 2026
GitHub stars
15,189GitHub, 15 Nov 2026
Forks
4,068GitHub, 15 Nov 2026
Latest release
v8.8.3GitHub, 15 Nov 2026
Released
22 Oct 2026GitHub
License
AGPL-3.0GitHub
First published on GitHub
12 Nov 2013GitHub

References

  • NVD https://nvd.nist.gov/vuln/detail/CVE-2026-86756
  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-86756
  • GitHub Advisory Database https://github.com/advisories/GHSA-68hq-m589-8q9j
  • github.com https://github.com/grokability/snipe-it/security/advisories/GHSA-68hq-m589-8q9j