Hatchet Security Update Addresses 4 Vulnerabilities
Tech GuruQuick Answer
The authority published GHSA-fjwv-jf2v-j499 for Hatchet packages and release streams identified in the project advisories. The project published 4 security advisories: Hatchet: SSRF via Unsigned UnsubscribeURL in SNS UnsubscribeConfirmation Handler; Hatchet: Cross-Tenant Durable Task Event Log Disclosure via Missing Authorization Check; Hatchet: Cross-tenant durable callback payload disclosure in Hatchet V1 Dispatcher; Hatchet DurableTask WorkerStatus gRPC resolves caller-supplied durable-task UUIDs via ListSatisfiedEntries with no tenant_id filter Affected deployments should be matched to the authority's exact scope and moved to the supported fixed release.
Confirm Scope And Apply The Supported Fix
What to do now: Inventory Hatchet packages and release streams identified in the project advisories, match the exact affected release or feature, apply the authority-supported fixed build or service remediation, validate the dependent workflow, and preserve evidence.
Last verified: 2026-09-23 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | Hatchet packages and release streams identified in the project advisories |
|---|---|
| Advisory | GHSA-fjwv-jf2v-j499 / GHSA-g26x-m427-f48f / GHSA-9q4h-f4x5-ffq8 / GHSA-992g-9cr3-vm5x |
| CVEs | CVE-2026-61681, CVE-2026-63342, CVE-2026-84298, CVE-2026-88978 |
| Authoritative release date | 2026-09-22 20:34:12 UTC |
| Authority revision date | 2026-09-22 20:40:48 UTC |
| Affected versions | hatchet-dev/hatchet < 0.91.1; github.com/hatchet-dev/hatchet < 0.91.1; github.com/hatchet-dev/hatchet < 0.95.3; github.com/hatchet-dev/hatchet < 0.106.1 |
| Fixed version | hatchet-dev/hatchet 0.91.1; github.com/hatchet-dev/hatchet 0.91.1; github.com/hatchet-dev/hatchet 0.95.3; github.com/hatchet-dev/hatchet 0.106.1 |
| CVSS base score | 3.1 / 4.1 / 4.3 / 6.3 (CVSS v3) |
| CVSS severity | Low to Medium |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
The project published 4 security advisories: Hatchet: SSRF via Unsigned UnsubscribeURL in SNS UnsubscribeConfirmation Handler; Hatchet: Cross-Tenant Durable Task Event Log Disclosure via Missing Authorization Check; Hatchet: Cross-tenant durable callback payload disclosure in Hatchet V1 Dispatcher; Hatchet DurableTask WorkerStatus gRPC resolves caller-supplied durable-task UUIDs via ListSatisfiedEntries with no tenant_id filter
What To Validate Now
- Inventory. Locate Hatchet packages and release streams identified in the project advisories deployments, versions, enabled features, exposure paths, owners, and dependent services.
- Establish applicability. Compare each deployment with the authority's affected-version statement: hatchet-dev/hatchet < 0.91.1; github.com/hatchet-dev/hatchet < 0.91.1; github.com/hatchet-dev/hatchet < 0.95.3; github.com/hatchet-dev/hatchet < 0.106.1 Do not infer applicability from product family or severity alone.
- Remediate. Apply hatchet-dev/hatchet 0.91.1; github.com/hatchet-dev/hatchet 0.91.1; github.com/hatchet-dev/hatchet 0.95.3; github.com/hatchet-dev/hatchet 0.106.1 through the supported vendor or project channel, following the current advisory and change-control requirements.
- Validate. Confirm the resulting version or managed-service state, exercise representative functionality and recovery paths, monitor for regressions, and document exceptions.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Use the exact supported release stream and repository. Test dependencies, clusters, integrations, and rollback before broad deployment; a CVSS rating or reachable feature is not evidence of exploitation.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
