GHSA-wmxc-v39r-p9wf
MEDIUMGHSA-wmxc-v39r-p9wf is a medium-severity (CVSS 4.4) Improper Input Validation vulnerability in github.com/temporalio/temporal. O3 Security confirms whether GHSA-wmxc-v39r-p9wf is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Temporal Server Denial of Service
Blast Radius
github.com/temporalio/temporal🐹github.com/temporalio/temporal🐹github.com/temporalio/temporalReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/temporalio/temporal | ≥ 1.22.0-rc1&&< 1.22.7 | 1.22.7 |
| 🐹Go | github.com/temporalio/temporal | ≥ 1.21.0&&< 1.21.6 | 1.21.6 |
| 🐹Go | github.com/temporalio/temporal | all versions | 1.20.5 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/temporalio/temporal. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/temporalio/temporal to 1.22.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wmxc-v39r-p9wf is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-wmxc-v39r-p9wf is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-wmxc-v39r-p9wf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-wmxc-v39r-p9wf in your dependencies?
O3 detects GHSA-wmxc-v39r-p9wf across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.