dbcve.org
HatchetApplication

CVE-2026-42572

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-14
Fix available
A fix is available. Upgrade to 0.83.39 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Hatchet is a platform for orchestrating background tasks, AI agents, and durable workflows at scale. Prior to 0.83.39, a missing authorization directive on the GET /api/v1/stable/dags/tasks endpoint caused Hatchet's tenant-membership check to be skipped for this route. A user authenticated to any tenant on the same Hatchet instance could query the endpoint with another tenant's UUID and a DAG UUID belonging to that tenant, and receive task metadata for that DAG. This vulnerability is fixed in 0.83.39.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A missing authorization directive on the GET /api/v1/stable/dags/tasks endpoint in Hatchet allows authenticated users to bypass tenant-membership validation. By providing another tenant's UUID and a DAG UUID from that tenant, users can retrieve task metadata belonging to a different tenant, resulting in cross-tenant information disclosure.

MitigationUpgrade to Hatchet version 0.83.39 or later, which includes the missing authorization directive to enforce tenant-membership checks on this endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
HatchetApplication
Affected:< 0.83.39

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Hatchet version
    Check the installed Hatchet version by querying the API health endpoint or inspecting the deployment manifests, Docker image tags, or Helm chart values. Compare against the affected range: < 0.83.39
    Affected if The installed version is lower than 0.83.39
  2. Confirm multi-tenancy is enabled
    Verify that the Hatchet instance has multi-tenancy configured. Check environment variables (such as MULTI_TENANCY_ENABLED or similar tenant-related configuration) or inspect the tenant configuration in the database. This vulnerability only affects multi-tenant deployments.
    Affected if Multi-tenancy is enabled and the instance hosts multiple tenants
  3. Verify API endpoint exposure
    Confirm the /api/v1/stable/dags/tasks endpoint is accessible. Check if this REST API is exposed externally or to untrusted users. Attempt a curl or HTTP request to the endpoint to verify it responds.
    Affected if The API endpoint is exposed to authenticated users outside the tenant isolation boundary
  4. Check authorization middleware configuration
    Inspect the Hatchet source code, deployment configuration, or API gateway settings to determine if tenant-membership validation is enforced on the /api/v1/stable/dags/tasks endpoint. Look for authorization directives or tenant context checks in the API route handler.
    Affected if No tenant-membership validation is present in the endpoint authorization logic

You are affected if Hatchet version is below 0.83.39, multi-tenancy is enabled, and the /api/v1/stable/dags/tasks endpoint is accessible to authenticated users without proper tenant-membership authorization checks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.83.39 or later
Fixed in 0.83.39
Interim mitigation

Upgrade to Hatchet version 0.83.39 or later, which includes the missing authorization directive to enforce tenant-membership checks on this endpoint.

Recommended fix High confidence

0.83.39 or later

  1. 1. Identify the current version of Hatchet running in your environment
  2. 2. Upgrade Hatchet to version 0.83.39 or later
  3. 3. Verify the upgrade was successful by checking the Hatchet version
  4. 4. Confirm the GET /api/v1/stable/dags/tasks endpoint now properly enforces tenant-membership authorization

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Hatchet Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42572 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-42572 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data