CVE-2026-16652: Temporal Server Schedule exclusion search can cause excessive CPU consumption
Temporal Technologies, Inc. · Temporal Server
Vendor fix available · Affected: Temporal Technologies, Inc. Temporal Server · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 40% of scored CVEs
DescriptionCVE.org
Temporal Server did not bound the work performed while searching for a Schedule's next action time. An authenticated caller with namespace write permission could create or update a Schedule that combines a fine-grained cadence with an exclusion calendar that rejects every candidate time, causing the server to evaluate excluded candidates without a per-search work budget. This can consume excessive CPU in Frontend and Schedule worker components. A persisted specification can also cause its backing Schedule Workflow to repeatedly fail and retry, allowing CPU consumption to continue without additional requests until the Schedule is deleted or its backing Workflow is terminated. Repeated or parallel exploitation can deny service. The issue affects availability only; it does not expose or modify Workflow data.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Temporal Technologies, Inc. · Temporal Serverfrom 1.17.0 up to and including 1.29.7; from 1.30.0 before 1.30.7; from 1.31.0 before 1.31.3
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Published
- September 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-16652 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.