---
id: CVE-2026-16652
title: >-
  Temporal Server did not bound the work performed while searching for a
  Schedule's next action time
summary: >-
  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 ex…
severity: high
cvss: 7.1
cvssVector: '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'
cwe:
  - CWE-606
vendor: 'Temporal Technologies, Inc.'
product: go.temporal.io/server
affected:
  - go.temporal.io/server >= 1.17.0 <= 1.29.7
  - go.temporal.io/server >= 1.30.0 < 1.30.7
  - go.temporal.io/server >= 1.31.0 < 1.31.3
published: '2026-09-21'
updated: '2026-09-22'
sourceUpdated: '2026-09-22T19:40:05.870'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-16652'
references:
  - url: >-
      https://github.com/temporalio/temporal/commit/c10c730e53ae394fffaefe44ba3722150fe40720
    label: security@temporal.io
  - url: 'https://github.com/temporalio/temporal/pull/11014'
    label: security@temporal.io
  - url: 'https://github.com/temporalio/temporal/releases/tag/v1.30.7'
    label: security@temporal.io
  - url: 'https://github.com/temporalio/temporal/releases/tag/v1.31.3'
    label: security@temporal.io
tags:
  - nvd
  - cve.org
epss: 0.00268
epssPercentile: 0.19197
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2026-09-21T15:32:53.335177Z'
cvssSource: cna
ingestedAt: '2026-09-21T11:35:54.435Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.