EUVD-2026-58095
GHSA-x7qq-m748-8p2c
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N
Network-delivered redirect requiring victim click; no attacker auth needed; scope changes to victim browser; integrity-only impact via host-separator bypass.
Primary rating from Vendor (https://github.com/getprobo/probo).
CVSS VectorVendor: https://github.com/getprobo/probo
Lifecycle Timeline
1DescriptionCVE.org
Impact
Probo's saferedirect package validates redirect URLs used across authentication flows (OIDC, SAML, session transfer, OAuth connectors, and trust-center magic links). The validator only inspected the second character of relative paths, so a URL like /../\evil.com passed validation because the second character is .. Go's http.Redirect normalizes this path to /\evil.com before setting the Location header. Browsers can interpret the backslash as a host separator and redirect the user to an external domain (https://evil.com), bypassing the intended same-origin restriction. This enables open-redirect phishing: an attacker can craft a continue parameter (or embed a malicious URL in a session-transfer token) that appears to originate from a trusted Probo domain but redirects victims elsewhere.
Patches
Fixed in go.probo.inc/probo by normalizing relative paths with path.Clean before validation, rejecting backslashes (including percent-encoded %5c) anywhere in the path, and re-checking the normalized result for protocol-relative and backslash prefixes.
Self-hosted deployments should upgrade to probod v0.194.1 or later.
SaaS deployments on getprobo.com are patched.
Workarounds
No practical workaround for self-hosted installations. Upgrade to the patched release.
AnalysisAI
Open redirect in Probo's saferedirect package allows unauthenticated remote attackers to bypass same-origin URL validation across all authentication flows - OIDC, SAML, session transfer, OAuth connectors, and trust-center magic links. A crafted URL such as /../\evil.com passes the flawed second-character check, and Go's http.Redirect normalizer collapses it to /\evil.com before setting the Location header; browsers then interpret the backslash as a host separator and navigate victims to an attacker-controlled domain. No public exploit is identified at time of analysis and the CVE carries no CISA KEV listing, but the authentication-flow context makes this a credible, high-value phishing vector. Self-hosted deployments must upgrade to probod v0.194.1.
Technical ContextAI
The root cause is CWE-601 (URL Redirection to Untrusted Site) in the saferedirect Go package (CPE: pkg:go/go.probo.inc_probo). The validator applied a single-character positional check on relative paths: it inspected only the second character, so /../\evil.com passed because position[1] is a period. Go's net/http.Redirect internally applies path.Clean-style normalization, collapsing /../\evil.com into /\evil.com before writing the Location response header. At that point validation has already succeeded. Chromium-based browsers and others on Windows treat a backslash following a leading slash as a protocol-relative host separator, rendering the response as a navigation to https://evil.com. The fix - shipping in probod v0.194.1 - applies path.Clean normalization before validation, explicitly rejects literal backslashes and percent-encoded equivalents (%5c anywhere in the path), and re-runs the normalized result through the prefix checks.
RemediationAI
Self-hosted deployments must upgrade to probod v0.194.1 or later, available from the upstream repository at https://github.com/getprobo/probo. The patched release normalizes relative paths with path.Clean before validation, rejects both literal and percent-encoded (%5c) backslashes anywhere in the path, and re-validates the normalized result for protocol-relative and backslash prefixes. The vendor explicitly states there is no practical workaround for self-hosted installations. As a partial, non-reliable compensating control, a reverse proxy or WAF rule that rejects requests where the continue or redirect parameter contains a literal or URL-encoded backslash would reduce but not eliminate exposure (percent-encoding variants may bypass naive string filters). Upgrading remains the only confirmed remediation. Advisory: https://github.com/getprobo/probo/security/advisories/GHSA-x7qq-m748-8p2c; additional context at https://github.com/getprobo/probo/blob/main/SECURITY_NOTES.md.
More in Open Redirect
View allA malicious third-party can give a crafted "ssh://..." URL to an unsuspecting victim, and an attempt to visit the URL ca
GFI Kerio Control versions 9.2.5 through 9.4.5 contain an HTTP response splitting vulnerability in the dest parameter of
PHP through 7.0.8 does not attempt to address RFC 3875 section 4.1.18 namespace conflicts and therefore does not protect
Multiple open redirect vulnerabilities in Apache Struts 2.0.0 through 2.3.15 allow remote attackers to redirect users to
Open redirect vulnerability in age-verification.php in the Age Verification plugin 0.4 and earlier for WordPress allows
Open redirect vulnerability in Kaseya Virtual System Administrator (VSA) 7.x before 7.0.0.29, 8.x before 8.0.0.18, 9.0 b
Vulnerability in the Oracle Applications Framework component of Oracle E-Business Suite (subcomponent: Popup windows (li
Unspecified vulnerability in the Oracle Application Server Single Sign-On component in Oracle Fusion Middleware 10.1.4.3
Flarum is open source discussion platform software. Rated medium severity (CVSS 6.5), this vulnerability is remotely exp
Open redirect vulnerability in Novius OS 5.0.1 (Elche) allows remote attackers to redirect users to arbitrary web sites
Open redirect vulnerability in the Redirect function in stageshow_redirect.php in the StageShow plugin before 5.0.9 for
Nteract v.0.28.0 was discovered to contain a remote code execution (RCE) vulnerability via the Markdown link. Rated crit
Vendor StatusVendor
SUSE
Severity: Moderate| Product | Status |
|---|---|
| SUSE Linux Enterprise Server 16.1 | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.1 | Affected |
| SUSE Linux Enterprise Module for Package Hub 15 SP5 | Affected |
| SUSE Linux Enterprise Module for Package Hub 15 SP6 | Affected |
| openSUSE Leap 15.5 | Affected |
| openSUSE Leap 15.6 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today