Quick answers
- Is CVE-2026-16652 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-16652 being exploited in the wild.
- How severe is CVE-2026-16652?
- Informational severity, published 21 September 2026.
- Which products and versions are affected?
- Temporal Technologies Temporal Server <unspecified; fix in commit c10c730.
- Is there a fix for CVE-2026-16652?
- A patch was published on 2026-07-15: Fix merged in commit c10c730 (List matching perf) Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-16652 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-16652?
- Check whether you run Temporal Technologies Temporal Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a resource exhaustion flaw in Schedule's next action time search logic. An authenticated user with namespace write permission can craft a Schedule specification with a fine-grained cadence and an exclusion calendar that rejects every candidate time, bypassing the per-search work budget. The malicious Schedule persists and causes the backing Schedule Workflow to repeatedly fail and retry, consuming CPU in Frontend and Schedule worker components without additional request overhead. Repeated or parallel exploitation amplifies the denial-of-service impact.
Affected products
- Temporal Technologies Temporal Server <unspecified; fix in commit c10c730
Timeline
- 2026-09-21: disclosed: CVE-2026-16652 published
- 2026-07-15: patched: Fix merged in commit c10c730 (List matching perf)