What is CVE-2026-54746?

CVE-2026-54746 is a medium-severity missing authorization vulnerability in github.com/hatchet-dev/hatchet (go), affecting versions >= 0.40.0, < 0.91.2. It is fixed in 0.91.2. The application does not perform an authorization check before performing a sensitive operation.

How severe is CVE-2026-54746?

CVE-2026-54746 has a CVSS score of 6.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of github.com/hatchet-dev/hatchet are affected by CVE-2026-54746?

github.com/hatchet-dev/hatchet (go) versions >= 0.40.0, < 0.91.2 is affected.

Is there a fix for CVE-2026-54746?

Yes. CVE-2026-54746 is fixed in 0.91.2. Upgrade to this version or later.

Is CVE-2026-54746 exploitable, and should I be worried?

Whether CVE-2026-54746 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-54746 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2026-54746 in github.com/hatchet-dev/hatchet

Q: How severe is CVE-2026-54746?

CVE-2026-54746 has a CVSS score of 6.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of github.com/hatchet-dev/hatchet are affected by CVE-2026-54746?

github.com/hatchet-dev/hatchet (go) versions >= 0.40.0, < 0.91.2 is affected.

Q: Is there a fix for CVE-2026-54746?

Yes. CVE-2026-54746 is fixed in 0.91.2. Upgrade to this version or later.

Q: Is CVE-2026-54746 exploitable, and should I be worried?

Whether CVE-2026-54746 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-54746 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-54746?

Upgrade github.com/hatchet-dev/hatchet to 0.91.2 or later.

Summary

Hatchet allows cross-tenant write/DoS to other tenants' workers via Dispatcher gRPC UpsertWorkerLabels and Unsubscribe

A cross-tenant write / DoS vulnerability in the Hatchet Dispatcher gRPC service allows any holder of a normal tenant-scoped API token (the lowest credential Hatchet issues, an OWNER of a brand-new tenant) to overwrite the affinity labels of, or disconnect from the dispatcher, any worker UUID belonging to any other tenant on the same Hatchet instance. The two affected RPCs, Dispatcher/UpsertWorkerLabels and Dispatcher/Unsubscribe, read the caller's tenant from the bearer-token context only for analytics and response shaping, and never use it to authorise the worker_id from the request body.

Impact

This CVE requires the attacker to successfully guess the target UUID.
Who is impacted. Any Hatchet deployment that hosts more than one tenant on the same instance:

Hatchet Cloud (multi-tenant SaaS), every tenant is exposed to every other tenant.
Self-hosted Hatchet with multiple internal teams / business units sharing one instance, each team is exposed to every other team on the box.
Any deployment where a single tenant's API token can be obtained by an attacker (e.g. a leaked low-privilege CI token from a single tenant). One token is enough to attack every other tenant on the same instance.

Single-tenant self-hosted deployments are unaffected in practice (the "victim" and "attacker" tenants would be the same).

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

CVE-2026-54746 has a CVSS score of 6.4 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.91.2); upgrading removes the vulnerable code path.

Affected versions

github.com/hatchet-dev/hatchet (>= 0.40.0, < 0.91.2)

Security releases

github.com/hatchet-dev/hatchet → 0.91.2 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade github.com/hatchet-dev/hatchet to 0.91.2 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-54746? CVE-2026-54746 is a medium-severity missing authorization vulnerability in github.com/hatchet-dev/hatchet (go), affecting versions >= 0.40.0, < 0.91.2. It is fixed in 0.91.2. The application does not perform an authorization check before performing a sensitive operation.
How severe is CVE-2026-54746? CVE-2026-54746 has a CVSS score of 6.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of github.com/hatchet-dev/hatchet are affected by CVE-2026-54746? github.com/hatchet-dev/hatchet (go) versions >= 0.40.0, < 0.91.2 is affected.
Is there a fix for CVE-2026-54746? Yes. CVE-2026-54746 is fixed in 0.91.2. Upgrade to this version or later.
Is CVE-2026-54746 exploitable, and should I be worried? Whether CVE-2026-54746 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-54746 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-54746? Upgrade github.com/hatchet-dev/hatchet to 0.91.2 or later.