cve.bz

CVE-2025-14986 temporal temporal: Incorrect Authorization

1.3 lowEPSS 0.4%Fix available

Low (1.3) in temporal temporal. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in go.temporal.io/server 1.27.4, 1.28.2, 1.29.2.

On this page
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.

Severity

CVSS 4.0

1.3 low
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U/S:N/AU:Y/R:U/RE:L/U:Green
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 38th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-01-02. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-863 Incorrect Authorization
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-14986 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-14986?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-14986?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-14986 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Temporalfrom 1.24.0 through 1.29.1
Temporalfrom 1.24.0 through 1.28.1
Temporalfrom 1.24.0 through 1.27.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-p2gr-hm8g-q772Gogo.temporal.io/server>=1.24.0 <1.27.41.27.4
GHSA-p2gr-hm8g-q772Gogo.temporal.io/server>=1.28.0 <1.28.21.28.2
GHSA-p2gr-hm8g-q772Gogo.temporal.io/server>=1.29.0 <1.29.21.29.2
GO-2025-4272Gogo.temporal.io/server>=1.24.0 <1.27.4
>=1.28.0 <1.28.2
>=1.29.0 <1.29.2
1.27.4, 1.28.2, 1.29.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
openSUSELeap 15.6govulncheck-vulndb0.0.20260114T191543-150000.1.137.1SUSE-SU-2026:0142-1
openSUSELeap 16.0govulncheck-vulndb0.0.20260723T184607-160000.1.1openSUSE-SU-2026:21483-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: openSUSE.

References

Check your stackJSON