Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%
Buy Us a Coffee

CVE-2026-16652— Temporal Server Schedule exclusion search can cause excessive CPU consumption

Quick assessment

Affected
Temporal Technologies, Inc. Temporal Server
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

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 r

CVSS 7.1 · High EPSS 0.27% · P19

Affected Version Matrix 3

VendorProduct Version RangeStatus
Temporal Technologies, Inc. Temporal Server 1.17.0≤ 1.29.7 affected
1.30.0< 1.30.7 affected
1.31.0< 1.31.3 affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-16652

Vulnerability Information

Shenlong is analyzing...

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Temporal Server Schedule exclusion search can cause excessive CPU consumption
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Source: CVE Program / CVE List V5
Vulnerability Type
循环条件输入未经检查
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
Temporal Technologies, Inc. Temporal Server 1.17.0 ~ 1.29.7 cpe:2.3:a:temporal:temporal:*:*:*:*:*:*:*:*

II. Public POCs for CVE-2026-16652

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-16652

请登录查看更多情报信息。

Patches & Fixes for CVE-2026-16652 (1)

Other References for CVE-2026-16652 (2)

Same Patch Batch · Temporal Technologies, Inc. · 2026-09-21 · 8 CVEs total

CVE-2026-89139 8.7 HIGH Temporal Server worker deployment compute provider executes a caller-supplied command on t
CVE-2026-65653 8.7 HIGH temporalio/tchannel-go zero-chunk call fragment causes process termination
CVE-2026-65654 8.7 HIGH temporalio/ringpop-go fails to enforce configured label limits on inbound membership gossi
CVE-2026-65652 8.7 HIGH temporalio/tchannel-go malformed checksum type causes process termination
CVE-2026-87858 7.2 HIGH Temporal Server completion callback source header can direct attacker-chosen requests to t
CVE-2026-16651 7.1 HIGH temporalio/sqlparser malformed MySQL version comments can cause a panic
CVE-2026-65651 6.0 MEDIUM temporalio/sqlparser deeply nested unary expressions can cause a fatal stack overflow duri

IV. Related Vulnerabilities

Same product: Temporal Server
Same vendor: Temporal Technologies, Inc.
Same weakness: CWE-606

V. Comments for CVE-2026-16652

No comments yet

Leave a comment