CVE-2026-42093

waiting for further signalsZero needs more public information before it can validate it.

GHSA-v43x-rgcc-wh77 ↗EUVD-2026-101515 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
getredash redash > 8.0.0, < 26.9.0
fixed in 26.9.0
CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
ETK-2026-1597Zero's internal tracking ID, independent of the CVE number., permanent identifier
6d 09h 43msince last run
30mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h06m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Redash releases after 8.0.0 through before 26.9.0 are affected by SQL injection in the Query Results query runner. An authenticated user with view-only access to both the Query Results and referenced data sources may execute SQL using the referenced data source's privileges.

mitigation

Upgrade Redash to version 26.9.0. Until upgraded, restrict user access to Query Results and referenced data sources.

fixed in 26.9.0

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.68%51st percentile
agent run time
30m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-14 18:00Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-14 18:00Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-42093

{
  "etk_id": "ETK-2026-1597",
  "cve_id": "CVE-2026-42093",
  "display_id": "CVE-2026-42093",
  "ghsa_id": "GHSA-v43x-rgcc-wh77",
  "euvd_id": "EUVD-2026-101515",
  "status": "published",
  "anchor_state": "anchored",
  "title": "SQL injection in Redash Query Results query runner",
  "summary": "Redash releases after 8.0.0 through before 26.9.0 are affected by SQL injection in the Query Results query runner. An authenticated user with view-only access to both the Query Results and referenced data sources may execute SQL using the referenced data source's privileges.",
  "mitigation": "Upgrade Redash to version 26.9.0. Until upgraded, restrict user access to Query Results and referenced data sources.",
  "vendor": "getredash",
  "product": "redash",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "> 8.0.0, < 26.9.0"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "26.9.0"
      ],
      "package_name": "Redash",
      "purl": null
    }
  ],
  "cwes": [
    89
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
  "epss_score": 0.0068,
  "epss_percentile": 0.5175,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 30.180316616666666,
  "t0_at": "2026-10-14T18:00:03.513000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-14T18:00:03.513000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-14T18:00:03.513000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-42093"
    }
  }
}

published 2026-10-14 18:36Z
last change 2026-10-21 04:45Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.