What is CVE-2024-2689?

CVE-2024-2689 is a medium-severity improper input validation vulnerability in github.com/temporalio/temporal (go), affecting versions >= 1.22.0-rc1, < 1.22.7. It is fixed in 1.22.7, 1.21.6, 1.20.5. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.

How severe is CVE-2024-2689?

CVE-2024-2689 has a CVSS score of 4.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/temporalio/temporal are affected by CVE-2024-2689?

github.com/temporalio/temporal (go) versions >= 1.22.0-rc1, < 1.22.7 is affected.

Is there a fix for CVE-2024-2689?

Yes. CVE-2024-2689 is fixed in 1.22.7, 1.21.6, 1.20.5. Upgrade to this version or later.

Is CVE-2024-2689 exploitable, and should I be worried?

Whether CVE-2024-2689 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-2024-2689 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-2024-2689 in github.com/temporalio/temporal

Q: How severe is CVE-2024-2689?

CVE-2024-2689 has a CVSS score of 4.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/temporalio/temporal are affected by CVE-2024-2689?

github.com/temporalio/temporal (go) versions >= 1.22.0-rc1, < 1.22.7 is affected.

Q: Is there a fix for CVE-2024-2689?

Yes. CVE-2024-2689 is fixed in 1.22.7, 1.21.6, 1.20.5. Upgrade to this version or later.

Q: Is CVE-2024-2689 exploitable, and should I be worried?

Whether CVE-2024-2689 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-2024-2689 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-2024-2689?

Upgrade: github.com/temporalio/temporal to 1.22.7 or later, github.com/temporalio/temporal to 1.21.6 or later, github.com/temporalio/temporal to 1.20.5 or later.

Summary

Temporal Server Denial of Service

Denial of Service in Temporal Server prior to version 1.20.5, 1.21.6, and 1.22.7 allows an authenticated user who has permissions to interact with workflows and has crafted an invalid UTF-8 string for submission to potentially cause a crashloop. If left unchecked, the task containing the invalid UTF-8 will become stuck in the queue, causing an increase in queue lag. Eventually, all processes handling these queues will become stuck and the system will run out of resources. The workflow ID of the failing task will be visible in the logs, and can be used to remove that workflow as a mitigation. Version 1.23 is not impacted. In this context, a user is an operator of Temporal Server.

Impact

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2024-2689 has a CVSS score of 4.4 (Medium). The vector is network-reachable, high 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 (1.22.7, 1.21.6, 1.20.5); upgrading removes the vulnerable code path.

Affected versions

github.com/temporalio/temporal (>= 1.22.0-rc1, < 1.22.7) github.com/temporalio/temporal (>= 1.21.0, < 1.21.6) github.com/temporalio/temporal (< 1.20.5)

Security releases

github.com/temporalio/temporal → 1.22.7 (go) github.com/temporalio/temporal → 1.21.6 (go) github.com/temporalio/temporal → 1.20.5 (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 the following packages to resolve this vulnerability:

github.com/temporalio/temporal to 1.22.7 or later; github.com/temporalio/temporal to 1.21.6 or later; github.com/temporalio/temporal to 1.20.5 or later

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

Frequently Asked Questions

What is CVE-2024-2689? CVE-2024-2689 is a medium-severity improper input validation vulnerability in github.com/temporalio/temporal (go), affecting versions >= 1.22.0-rc1, < 1.22.7. It is fixed in 1.22.7, 1.21.6, 1.20.5. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
How severe is CVE-2024-2689? CVE-2024-2689 has a CVSS score of 4.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/temporalio/temporal are affected by CVE-2024-2689? github.com/temporalio/temporal (go) versions >= 1.22.0-rc1, < 1.22.7 is affected.
Is there a fix for CVE-2024-2689? Yes. CVE-2024-2689 is fixed in 1.22.7, 1.21.6, 1.20.5. Upgrade to this version or later.
Is CVE-2024-2689 exploitable, and should I be worried? Whether CVE-2024-2689 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-2024-2689 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-2024-2689?
- Upgrade github.com/temporalio/temporal to 1.22.7 or later
- Upgrade github.com/temporalio/temporal to 1.21.6 or later
- Upgrade github.com/temporalio/temporal to 1.20.5 or later