Unchecked Input for Loop Condition Affecting github.com/temporalio/temporal/service/worker/scheduler package, versions >=1.17.0 <1.30.7>=1.31.0 <1.31.3
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-GOLANG-GITHUBCOMTEMPORALIOTEMPORALSERVICEWORKERSCHEDULER-20078931
- published24 Sept 2026
- disclosed21 Sept 2026
Introduced: 21 Sep 2026
NewCVE-2026-16652 Â (opens in a new tab)How to fix?
Upgrade github.com/temporalio/temporal/service/worker/scheduler to version 1.30.7, 1.31.3 or higher.
Overview
Affected versions of this package are vulnerable to Unchecked Input for Loop Condition due to unbounded next-action-time search in the schedule spec evaluation logic in service/worker/scheduler/spec.go and the scheduler/frontend list-matching-time paths. An authenticated caller with namespace write permission can create or update a Schedule whose calendar matches frequently but whose exclusion calendar rejects every candidate time, causing the server to keep scanning excluded candidates and burn excessive CPU in the frontend and schedule worker components. If the over-excluded spec is persisted, the backing Schedule Workflow can keep failing and retrying the same expensive search, so the CPU cost continues without additional requests until the Schedule is deleted or its workflow is terminated.