# CVE-2026-120091 — Temporal Server

> As of 2026-11-03, CVE-2026-120091 is a High-severity (band derived from the CVSS v4.0 score, not stated by the CNA) vulnerability in Temporal Server, CVSS v4.0 8.7, EPSS 0.4% (41.2th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-120091 as of 2026-11-03; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-11-03

## What is CVE-2026-120091?

Temporal Server compiles a Worker Controller Instance module, go.temporal.io/auto-scaled-workers, into its Worker Service, and that module registers a compute provider named k8s whose function is to manage workers running in a Kubernetes cluster. The k8s provider built its Kubernetes client from the client configuration supplied in the caller's request rather than from operator configuration, and building and using that client could run a command of the caller's choosing on the Worker Service host, under the account the server process runs as. Two frontend operations reach the provider. CreateWorkerDeploymentVersion requires a namespace write role. ValidateWorkerDeploymentVersionComputeConfig is registered as a read-only namespace operation, so an authenticated caller holding only a read role in a single namespace can reach the provider through it, and that route does not require a worker deployment to already exist. Execution happens while the submitted configuration is validated, so no scaling decision, task arrival, or unusual request sequence is required. Because the Worker Service process holds the persistence credentials for every namespace in the cluster and the cluster's TLS material, the consequence reaches beyond the caller's namespace to the cluster as a whole. The provider is present in the official temporal-server binaries and container images for the affected releases. The control that keeps it unreachable is the compute provider allowlist, the dynamic configuration setting workercontroller.compute_providers.enabled. On Temporal Server 1.31.0 through 1.31.2 that allowlist does not deny by default: when the setting is unset the check is skipped and every registered compute provider is permitted, k8s included, so a stock deployment of those releases is exposed. On 1.31.3 and later 1.31 releases, and on 1.32.0 and later 1.32 releases, the allowlist denies by default, and a deployment is exposed only where k8s has been added to it. The 1.30 release line does not include the Worker Controller Instance module and is unaffected. To determine whether a deployment is affected, check the following together. The deployed Temporal Server version is in an affected range. The Worker Service is running, which it is in the default service set and therefore in a stock deployment. The effective value of workercontroller.compute_providers.enabled contains k8s, or, on 1.31.0 through 1.31.2 only, is unset; check both the global value and every namespace-constrained override, because an override can add k8s for a single namespace. And authorization is configured, meaning a real authorizer and claim mapper are in place; a deployment running with no authorizer already grants every caller unrestricted access to every namespace, so it has no namespace boundary for this to cross. Deployments that use a custom authorizer should also check whether it permits ValidateWorkerDeploymentVersionComputeConfig to callers without namespace write access. The separate per-namespace dynamic configuration setting workercontroller.enabled does not gate the affected path on any affected release.

The record classifies CVE-2026-120091 under weakness classes [CWE-78](https://intel.threadlinqs.com/cwe/CWE-78), [CWE-749](https://intel.threadlinqs.com/cwe/CWE-749), [CWE-1188](https://intel.threadlinqs.com/cwe/CWE-1188), [CWE-863](https://intel.threadlinqs.com/cwe/CWE-863). 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 17 days ago.

## Severity and exploitation probability

- **CVSS v4.0 base score:** 8.7 — High (derived from score) (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **EPSS (FIRST):** 0.4% probability of exploitation in the next 30 days, higher than 41.2% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 6/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-11-02

## Is CVE-2026-120091 being exploited?

It currently carries a trending score of 40 in the Threadlinqs vulnerability feed.

## Affected products and versions

- **Temporal Technologies, Inc.**: Temporal Server

## How to fix CVE-2026-120091

Patch reference: [https://github.com/temporalio/temporal-auto-scaled-workers/pull/165](https://github.com/temporalio/temporal-auto-scaled-workers/pull/165). Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

## Threat activity tracking CVE-2026-120091

No threat campaign in the Threadlinqs corpus currently references CVE-2026-120091, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD, FIRST EPSS. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [github.com — release notes](https://github.com/temporalio/temporal/releases/tag/v1.32.2)
- [github.com — release notes (v1.31)](https://github.com/temporalio/temporal/releases/tag/v1.31.5)
- [github.com — patch](https://github.com/temporalio/temporal-auto-scaled-workers/pull/165)
- [github.com — patch (12843)](https://github.com/temporalio/temporal/pull/12843)

**Other references**

- [cve.org](https://www.cve.org/CVERecord?id=CVE-2026-89139)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-120091
No Threadlinqs detection currently covers CVE-2026-120091; it is re-checked on every ingest.
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp
