hatchet-dev hatchet up to 0.83.37 tasks authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in hatchet-dev hatchet up to 0.83.37. Affected by this vulnerability is an unknown functionality of the file /api/v1/stable/dags/tasks. Executing a manipulation can lead to authorization. This vulnerability is handled as CVE-2026-42572. The attack can be executed remotely. There is not any exploit available. You should upgrade the affected component.
Details
A vulnerability has been found in hatchet-dev hatchet up to 0.83.37 and classified as problematic. This vulnerability affects some unknown functionality of the file /api/v1/stable/dags/tasks. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. As an impact it is known to affect confidentiality. CVE summarizes:
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.
The advisory is available at github.com. This vulnerability was named CVE-2026-42572 since 04/28/2026. The exploitation appears to be difficult. The attack can be initiated remotely. Technical details are known, but there is no available exploit.
Upgrading to version 0.83.38 eliminates this vulnerability.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
- 0.83.0
- 0.83.1
- 0.83.2
- 0.83.3
- 0.83.4
- 0.83.5
- 0.83.6
- 0.83.7
- 0.83.8
- 0.83.9
- 0.83.10
- 0.83.11
- 0.83.12
- 0.83.13
- 0.83.14
- 0.83.15
- 0.83.16
- 0.83.17
- 0.83.18
- 0.83.19
- 0.83.20
- 0.83.21
- 0.83.22
- 0.83.23
- 0.83.24
- 0.83.25
- 0.83.26
- 0.83.27
- 0.83.28
- 0.83.29
- 0.83.30
- 0.83.31
- 0.83.32
- 0.83.33
- 0.83.34
- 0.83.35
- 0.83.36
- 0.83.37
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.2VulDB Meta Temp Score: 4.1
VulDB Base Score: 3.1
VulDB Temp Score: 3.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.3
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-639 / CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: hatchet 0.83.38
Timeline
04/28/2026 CVE reserved05/14/2026 Advisory disclosed
05/14/2026 VulDB entry created
05/14/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-42572 (🔒)
GCVE (CVE): GCVE-0-2026-42572
GCVE (VulDB): GCVE-100-363946
Entry
Created: 05/14/2026 20:06Changes: 05/14/2026 20:06 (63)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.