Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-49820 medium CVSS 4.7

Open Redirect in go.probo.inc/probo (CVE-2026-49820)

Summary

Vulnerability in go.probo.inc/probo (CVE-2026-49820). Risk of unauthorized operations or information disclosure. Exploitable via saferedirect. Mitigation: upgrade to 0.204.0 or later.

Original description

The description as published by the source.

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.

Source: GitHub Security Advisories (Global) 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-49820 has been found in go.probo.inc/probo.
Attackers can target a specific entry point like saferedirect over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.7/10.
What to do: upgrade go.probo.inc/probo to 0.204.0 or later.
If unsure, ask your IT team or search "go.probo.inc/probo CVE-2026-49820" on the vendor's site.

CVE-2026-49820 (go.probo.inc/probo) — CWE-601 / CVSS v3 4.7
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: saferedirect / http.Redirect / Location / continue
Patched: 0.204.0 — apply immediately
Workaround: No practical workaround for self-hosted installations.
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

A vulnerability (CWE-601) exists in go.probo.inc/probo. Attackers reach the vulnerable code path via saferedirect without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of go.probo.inc/probo. Attack surface: saferedirect / http.Redirect / Location / continue.

🔥 Severity

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

🔧 How to fix

Update to 0.204.0.

🛡️ Workaround

Workaround: No practical workaround for self-hosted installations.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'go.probo.inc/probo' . 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 'go.probo.inc/probo' . | grep -v node_modules

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

  2. 2
    Apply temporary workaround mitigate 
    No practical workaround for self-hosted installations.

    パッチが適用されるまでの応急処置として、No practical workaround for self-hosted installations. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade go.probo.inc/probo to 0.204.0

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

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

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

Affected packages

go go.probo.inc/probo
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.204.0"}]}]

References

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