Redash is a package for data visualization and sharing. From 10.0.0 until 26.9.0, the JSON data source query runner in redash/query_runner/json_ds.py used _get_all_results() to combine its configured base_url with a user-supplied query URL by using urljoin. An absolute query URL replaced the configured base URL instead of remaining under it, allowing a user with execute_query permission to direct a server-side request to an arbitrary external origin. When HTTP Basic Auth was configured for the data source, the request also forwarded those credentials to the selected origin. Private and internal address access remained constrained when REDASH_ENFORCE_PRIVATE_IP_BLOCK was enabled. This issue is fixed in version 26.9.0.
CVE-2026-76083
MEDIUMPre-NVD 4.94.9Trending — 3 sources updated this week
EchelonGraph scoreMEDIUM confidence
“—” beside the score: it is equal to the CVSS score beside it.
This medium-severity CVE scores 4.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (34th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
4.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 4.9Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 4.9
- EG Score
- 4.9MEDIUMmedium confidence
- EG Risk
- 22EG Risk 22/100
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 (value × EchelonGraph’s weight)Severity49% × 45%The EG Score, 4.9 of 10.Exploitation0.4% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.4%
- EPSS %ILE
- 34th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 14, 2026
Last Modified
October 16, 2026
Advisory Details (3)
Auto-updated Oct 15, 2026Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available
v26.9.0
Patch available: getredash/redash v26.9.0
https://github.com/getredash/redash/releases/tag/v26.9.0GitHub commit Patch Available
commit 2be9552d7e87 (getredash/redash)
Patch available: getredash/redash v26.9.0 (contains commit 2be9552d7e87)
https://github.com/getredash/redash/commit/2be9552d7e87bc3be76016e183a9f593e33073c7GitHub advisoryMentions a patch (unverified)
JSON data source query URL can bypass base URL restriction · Advisory · getredash/redash · GitHub
https://github.com/getredash/redash/security/advisories/GHSA-m723-r867-wfgwWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-10-16 20:13 UTCEG score recompute
- 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-15 16:37 UTCEG score recompute
- 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-15 15:29 UTCEG score recompute
- 2026-10-14 18:44 UTCEG score recompute
- 2026-10-14 18:17 UTCEG score recomputeFirst assessed: 4.9 MEDIUM
- 2026-10-14 18:15 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-76083?
CVE-2026-76083 is a medium-severity vulnerability; its CVE record was published on October 14, 2026. Redash is a package for data visualization and sharing. From 10.0.0 until 26.9.0, the JSON data source query runner in redash/queryrunner/jsonds.py used getallresults() to combine its configured baseurl with a user-supplied query URL by using urljoin. An absolute query URL replaced the configured…
When was the CVE record for CVE-2026-76083 published?
The CVE record for CVE-2026-76083 was published on October 14, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 16, 2026; the record at its source may have been updated since.
Is CVE-2026-76083 actively exploited?
CVE-2026-76083 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-76083?
CVE-2026-76083 has a CVSS base score of 4.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-76083?
A fix for CVE-2026-76083 is available: update to the fixed version the vendor names in its advisory.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-76083
Is Your Infrastructure Affected by CVE-2026-76083?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.