{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-76083 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-76083 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-76083 is a medium-severity server-side request forgery vulnerability in getredash redash, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-76083 and fix it if it is affected.\n\nWhat it is: CVE-2026-76083 is a medium-severity server-side request forgery vulnerability in getredash redash, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-76083 in the wild and no public exploit code.\n\nAffected product: getredash redash. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-76083/ (Markdown: https://insights.sbomify.com/CVE-2026-76083/index.md)","id":"CVE-2026-76083","markdown":"https://insights.sbomify.com/CVE-2026-76083/index.md","name":"CVE-2026-76083","record":{"aliases":["GHSA-m723-r867-wfgw"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Redash data visualization","requires_auth":"low_privilege","summary":"An attacker with query execution permissions can bypass base URL restrictions to send server-side requests to arbitrary external origins, potentially leaking credentials.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:H/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Redash: JSON data source query URL can bypass base URL restriction","id":"CVE-2026-76083","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Formie: Integration form-settings action allows SSRF and exfiltration of stored integration credentials","id":"CVE-2026-76086"},"packages":[],"prev":{"headline":"ZITADEL: Improper Role Revocation on Granted Projects during Multiple Role Deletions","id":"CVE-2026-76081"},"products":["redash"],"published":"2026-10-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["getredash"]},"summary":"An attacker with query execution permissions can bypass base URL restrictions to send server-side requests to arbitrary external origins, potentially leaking credentials.","url":"https://insights.sbomify.com/CVE-2026-76083/"}