CVE-2025-14986 Affecting temporal-fips package, versions <1.5.1-r4
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-CHAINGUARDLATEST-TEMPORALFIPS-14890034
- published7 Jan 2026
- disclosed30 Dec 2025
Introduced: 30 Dec 2025
CVE-2025-14986 (opens in a new tab)How to fix?
Upgrade Chainguard temporal-fips to version 1.5.1-r4 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream temporal-fips package and not the temporal-fips package as distributed by Chainguard.
See How to fix? for Chainguard relevant fixed versions and status.
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.