⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Medium · CVSS 5.3

How to Fix CVE-2026-42572: Insecure Direct Object Reference in hatchet

Other vulnerabilities in the same area that are worth patching alongside this one:

*By Sai Kiran Pandrala*

⚡ At a glance
SeverityCVSS 5.3 - Medium
Actively exploited?Not currently listed in CISA KEV
Affected< 0.83.38
Fixed in0.83.39.
Type (CWE)CWE-639: Authorization Bypass Through User-Controlled Key

What is CVE-2026-42572?

CVE-2026-42572 is an insecure direct object reference (IDOR) in hatchet. The product uses a user-supplied identifier to fetch or modify a record without checking that the caller is allowed to touch that specific object, exposing or altering other users' data. Vendor description: 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.

Why this CVE matters

IDOR flaws bypass the application's intended tenant isolation. In multi-user products this typically means one customer can read or modify another customer's data with nothing more than a sequential identifier.

For deployments of hatchet that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

Open hatchet's About dialog or run the vendor-documented version-check command. Compare the result against the affected ranges in the advisory.

How to fix CVE-2026-42572

  1. Read the vendor advisory in full: https://github.com/hatchet-dev/hatchet/security/advisories/GHSA-55gc-6fmc-fpx9
  2. Upgrade hatchet to the patched build listed in the vendor advisory.
  3. Back up the configuration (and database, where applicable) before upgrading.
  4. Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
  5. Restart the affected service so the patched binary loads, then verify the new version (see verification section).

Upgrade hatchet-dev hatchet


# CVE-2026-42572 affects hatchet < 0.83.38.
# Fixed in 0.83.38. Vendor advisory: https://github.com/hatchet-dev/hatchet/security/advisories/GHSA-55gc-6fmc-fpx9

# 1. Identify the running version using the vendor-documented command.
#    (Open the product UI -> About, or run the CLI version probe.)

# 2. Stage the patched build named in the advisory.
#    Vendor advisory: https://github.com/hatchet-dev/hatchet/security/advisories/GHSA-55gc-6fmc-fpx9

# 3. Apply the upgrade. If the vendor ships a Linux package, pull it via your
#    distribution's package manager:
sudo apt update && sudo apt install --only-upgrade hatchet        # Debian / Ubuntu
sudo dnf upgrade hatchet                                          # RHEL / Rocky / Alma / Fedora

# 4. Restart the affected service so the new binary loads.
sudo systemctl restart hatchet 2>/dev/null || true

# 5. Re-run the version probe and confirm it matches 0.83.38.


# Windows-hosted installs of hatchet: apply via PSWindowsUpdate or the vendor MSI.
Install-Module PSWindowsUpdate -Force -SkipPublisherCheck -Confirm:$false
Get-WindowsUpdate -AcceptAll -Install -AutoReboot

Verify the fix landed


# CVE-2026-42572 verification checklist.

# 1. Confirm the running version matches 0.83.38 (replace the version probe with
#    the platform-specific command shown above).

# 2. Re-scan the host with your vulnerability scanner (Nessus, Qualys, Tenable,
#    OpenVAS, Wazuh). The scanner must no longer flag CVE-2026-42572.

# 3. Inspect recent service and kernel logs for crash-loops or rollback events.
journalctl -u <service-name> --since "10 minutes ago"
dmesg --since "10 minutes ago"

# 4. Cross-check the running build against the vendor advisory:
#    https://github.com/hatchet-dev/hatchet/security/advisories/GHSA-55gc-6fmc-fpx9

If you cannot patch immediately

Front the vulnerable endpoint with an authorization rule at a reverse proxy or API gateway that validates the caller's right to access the requested object. The patch is the only complete fix.

How to verify the fix worked

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for log entries that do not match your normal request patterns, especially repeated requests to the same uncommon endpoint, and any administrative changes you cannot tie back to a known operator.

Frequently asked questions

Is CVE-2026-42572 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Will a WAF or IDS rule fully mitigate CVE-2026-42572?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

How long should I plan for the upgrade?

Typical vendor-documented upgrade windows for hatchet run from a few minutes to under an hour depending on cluster size. Test in a staging environment first and follow the vendor's documented HA upgrade order.

References

*This guide was assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*