Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

ExecuteMultiOperation Namespace Policy Bypass

cve-program · CVE-2025-14986

Published

When frontend.enableExecuteMultiOperation is enabled, the server can apply namespace-scoped validation and feature gates for the embedded StartWorkflowExecutionRequest using its Namespace field rather than the outer, authorized ExecuteMultiOperationRequest.Namespace. This allows a caller authorized for one namespace to bypass that namespace's limits/policies by setting the embedded start request's namespace to a different namespace. The workflow is still created in the outer (authorized) namespace; only validation/gating is performed under the wrong namespace context. This issue affects Temporal: from 1.24.0 through 1.29.1. Fixed in 1.27.4, 1.28.2, 1.29.2.

Read the publisher's advisory

euvd · EUVD-2025-205854

Published

When frontend.enableExecuteMultiOperation is enabled, the server can apply namespace-scoped validation and feature gates for the embedded StartWorkflowExecutionRequest using its Namespace field rather than the outer, authorized ExecuteMultiOperationRequest.Namespace. This allows a caller authorized for one namespace to bypass that namespace's limits/policies by setting the embedded start request's namespace to a different namespace. The workflow is still created in the outer (authorized) namespace; only validation/gating is performed under the wrong namespace context. This issue affects Temporal: from 1.24.0 through 1.29.1. Fixed in 1.27.4, 1.28.2, 1.29.2.

Read the publisher's advisory

nvd · CVE-2025-14986

Published

When frontend.enableExecuteMultiOperation is enabled, the server can apply namespace-scoped validation and feature gates for the embedded StartWorkflowExecutionRequest using its Namespace field rather than the outer, authorized ExecuteMultiOperationRequest.Namespace. This allows a caller authorized for one namespace to bypass that namespace's limits/policies by setting the embedded start request's namespace to a different namespace. The workflow is still created in the outer (authorized) namespace; only validation/gating is performed under the wrong namespace context. This issue affects Temporal: from 1.24.0 through 1.29.1. Fixed in 1.27.4, 1.28.2, 1.29.2.

Read the publisher's advisory

osv · GHSA-p2gr-hm8g-q772

Published

When frontend.enableExecuteMultiOperation is enabled, the server can apply namespace-scoped validation and feature gates for the embedded StartWorkflowExecutionRequest using its Namespace field rather than the outer, authorized ExecuteMultiOperationRequest.Namespace. This allows a caller authorized for one namespace to bypass that namespace's limits/policies by setting the embedded start request's namespace to a different namespace. The workflow is still created in the outer (authorized) namespace; only validation/gating is performed under the wrong namespace context. This issue affects Temporal: from 1.24.0 through 1.29.1. Fixed in 1.27.4, 1.28.2, 1.29.2.

Read the publisher's advisory

osv · GO-2025-4272

Published

Temporal has a namespace policy bypass allowing requests to be authorized for incorrect contexts in go.temporal.io/server

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2025-14986

Published

temporal

https://github.com/temporalio/temporal

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "collectionURL": "https://github.com/temporalio/temporal",
                    "defaultStatus": "unaffected",
                    "packageName": "temporal",
                    "product": "Temporal",
                    "repo": "https://github.com/temporalio/temporal",
                    "vendor": "Temporal",
                    "versions": [
                        {
                            "lessThanOrEqual": "1.29.1",
                            "status": "affected",
                            "version": "1.24.0",
                            "versionType": "semver"
                        },
                        {
                            "lessThanOrEqual": "1.28.1",
                            "status": "affected",
                            "version": "1.24.0",
                            "versionType": "semver"
                        },
                        {
                            "lessThanOrEqual": "1.27.3",
                            "status": "affected",
                            "version": "1.24.0",
                            "versionType": "semver"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2025-205854

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Dec 30, 2025, 8:17:47 PM

dateUpdated: Jan 2, 2026, 3:31:02 PM

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2025-14986

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Deferred

Weakness classifications: CWE-863

Original publisher date fields

published: 2025-12-30T21:15:42.773

lastModified: 2026-06-17T08:36:53.560

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-p2gr-hm8g-q772

Published

go.temporal.io/server

Go

SEMVER · introduced 1.24.0 → fixed 1.27.4

go.temporal.io/server

Go

SEMVER · introduced 1.28.0 → fixed 1.28.2

go.temporal.io/server

Go

SEMVER · introduced 1.29.0 → fixed 1.29.2

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GO-2025-4272

Published

go.temporal.io/server

Go

SEMVER · introduced 1.24.0 → fixed 1.27.4 → introduced 1.28.0 → fixed 1.28.2 → introduced 1.29.0 → fixed 1.29.2

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 11:47 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current