CVE-2026-66084

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

GHSA-26vh-p5jc-q2mg ↗EUVD-2026-94806 ↗

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.
Apache Software Foundation Apache DolphinScheduler < 3.4.3
fixed in 3.4.3
CWE-863 Incorrect Authorization
ETK-2026-2241Zero's internal tracking ID, independent of the CVE number., permanent identifier
4h 32msince last run
24mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+303h22m
0
+2h
+4h
+6h
+8h
+10h

description

Apache DolphinScheduler API versions before 3.4.3 do not properly enforce project ownership when updating task definitions. An authenticated user with access to a project may modify task definitions and dependency relationships in a different project, affecting workflow integrity and execution.

mitigation

Upgrade org.apache.dolphinscheduler:dolphinscheduler-api to version 3.4.3 or later.

fixed in 3.4.3

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.
–
agent run time
24m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-08 08:18Z
Δ 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-08 08:18Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2241",
  "cve_id": "CVE-2026-66084",
  "display_id": "CVE-2026-66084",
  "ghsa_id": "GHSA-26vh-p5jc-q2mg",
  "euvd_id": "EUVD-2026-94806",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Cross-project authorization bypass in DolphinScheduler",
  "summary": "Apache DolphinScheduler API versions before 3.4.3 do not properly enforce project ownership when updating task definitions. An authenticated user with access to a project may modify task definitions and dependency relationships in a different project, affecting workflow integrity and execution.",
  "mitigation": "Upgrade org.apache.dolphinscheduler:dolphinscheduler-api to version 3.4.3 or later.",
  "vendor": "Apache Software Foundation",
  "product": "Apache DolphinScheduler",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 3.4.3"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "3.4.3"
      ],
      "package_name": "org.apache.dolphinscheduler:dolphinscheduler-api",
      "purl": null
    }
  ],
  "cwes": [
    863
  ],
  "cvss_score": 8.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 24.402528783333334,
  "t0_at": "2026-10-08T08:18:19.410000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-08T08:18:19.410000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-08T08:18:19.410000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-66084"
    }
  }
}

published 2026-10-20 23:16Z
last change 2026-10-21 03:26Z

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.