← Back
CVE-2026-49820
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.
AI summary snake-internal / snake-material-v2
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: ?/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 /
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
go.probo.inc/probo — . Attack surface: `saferedirect` / `http.Redirect` / `Location` / `continue`.
🔥 Severity
Severity: ?. 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 (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify 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 し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
No practical workaround for self-hosted installations.パッチが適用されるまでの応急処置として、No practical workaround for self-hosted installations. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade go.probo.inc/probo to 0.204.0ステージング環境で 0.204.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
go.probo.inc/probo
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.204.0"}]}]