CVE-2026-49820

MEDIUMPre-NVD 4.74.7—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
4.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Probo is a self-hostable governance, risk, and compliance (GRC) platform built for engineering and security teams. Probo's saferedirect package validates redirect URLs used across authentication flows (OIDC, SAML, session transfer, OAuth connectors, and trust-center magic links). Prior to version 0.19.3.1, 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. This is fixed in go.probo.inc/probo 0.193.1 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. No practical workaround is available for self-hosted installations.

CVSS v3
4.7
EG Score
4.7(medium)
EG Risk
21(Track)
EG Risk 21/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity47% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

Published

June 30, 2026

Last Modified

August 14, 2026

Advisory Details (2)

Auto-updated Aug 13, 2026
Patch available. Sources: github.
github Patch Available

Open redirect bypass via path normalization · Advisory · getprobo/probo · GitHub

https://github.com/getprobo/probo/security/advisories/GHSA-x7qq-m748-8p2c
generic

probo/SECURITY_NOTES.md at main · getprobo/probo · GitHub

https://github.com/getprobo/probo/blob/main/SECURITY_NOTES.md

Vendor Advisories for CVE-2026-49820(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
go.probo.inc/probo—0.204.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 39× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 14:35 UTCEG score recompute
  6. 2026-09-06 13:47 UTCEPSS rescore
  7. 2026-09-04 05:06 UTCEPSS rescore
  8. 2026-09-02 14:12 UTCEPSS rescore
  9. 2026-09-01 13:54 UTCEPSS rescore
  10. 2026-09-01 04:40 UTCEPSS rescore
  11. 2026-08-30 19:17 UTCEPSS rescore
  12. 2026-08-30 18:02 UTCEG score recompute
  13. 2026-08-30 01:22 UTCEPSS rescore
  14. 2026-08-28 21:41 UTCEPSS rescore
  15. 2026-08-27 22:41 UTCEG score recompute
  16. 2026-08-27 14:25 UTCEPSS rescore
  17. 2026-08-26 14:46 UTCEPSS rescore
  18. 2026-08-25 13:49 UTCEPSS rescore
  19. 2026-08-24 12:39 UTCEG score recompute
  20. 2026-08-23 10:26 UTCEG score recompute
  21. 2026-08-23 00:19 UTCEPSS rescore
  22. 2026-08-22 08:47 UTCEG score recompute
  23. 2026-08-21 23:49 UTCEPSS rescore
  24. 2026-08-21 07:11 UTCEG score recompute
  25. 2026-08-20 22:55 UTCEPSS rescore
Show 18 more
  1. 2026-08-20 05:30 UTCEG score recompute
  2. 2026-08-19 17:04 UTCEPSS rescore
  3. 2026-08-19 01:37 UTCEG score recompute
  4. 2026-08-18 13:48 UTCEPSS rescore
  5. 2026-08-18 00:01 UTCEG score recompute
  6. 2026-08-17 13:47 UTCEPSS rescore
  7. 2026-08-16 19:56 UTCEG score recompute
  8. 2026-08-16 14:56 UTCEPSS rescore
  9. 2026-08-16 02:14 UTCEPSS rescore
  10. 2026-08-15 18:08 UTCEG score recompute
  11. 2026-08-15 01:30 UTCEPSS rescore
  12. 2026-08-14 16:32 UTCEG score recompute
  13. 2026-08-14 16:04 UTCEG score recompute
  14. 2026-08-13 15:28 UTCEG score recompute
  15. 2026-07-30 23:57 UTCEG score recompute
  16. 2026-07-26 13:51 UTCEG score recompute
  17. 2026-07-23 03:18 UTCEG score recompute
  18. 2026-06-30 19:31 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-49820?
CVE-2026-49820 is a medium vulnerability published on June 30, 2026. Probo is a self-hostable governance, risk, and compliance (GRC) platform built for engineering and security teams. Probo's saferedirect package validates redirect URLs used across authentication flows (OIDC, SAML, session transfer, OAuth connectors, and trust-center magic links). Prior to version…
When was CVE-2026-49820 disclosed?
CVE-2026-49820 was first published in the National Vulnerability Database on June 30, 2026, with the most recent update on August 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49820 actively exploited?
CVE-2026-49820 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 78.5% of all scored CVEs.
What is the CVSS score of CVE-2026-49820?
CVE-2026-49820 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2026-49820?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49820, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49820

Explore →

Is Your Infrastructure Affected by CVE-2026-49820?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs