Temporal Server Schedule exclusion search can cause excessive CPU consumption (CVE-2026-16652) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-16652

Temporal Server Schedule exclusion search can cause excessive CPU consumption

Answer in brief

CVE-2026-16652 records a Unknown severity vulnerability in Temporal Server Schedule exclusion search can cause excessive CPU consumption. The current sources do not mark it as known exploited. The current feed maps Temporal Technologies, Inc./Temporal Server (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 21, 2026Updated Sep 21, 2026Source checked Sep 21, 2026First seen by HOL Sep 21, 2026Material review Sep 21, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Temporal Technologies, Inc./Temporal Server (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Temporal Technologies, Inc./Temporal Servergeneric	1.17.0 \|\| >=1.30.0 <1.30.7 \|\| >=1.31.0 <1.31.3	1.30.7, 1.31.3

Recommended response

Check inventory. Check lockfiles and deployed manifests for Temporal Technologies, Inc./Temporal Server.
Review the reported fix. Update Temporal Technologies, Inc./Temporal Server to 1.30.7 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 21, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 21, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 21, 2026

Sources and claim methodology

Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.