Temporal has an Incorrect Authorization vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

5.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L · score source

EPSS

• CVE-2025-14987: 0.40% estimated exploitation activity in the next 30 days; percentile 34.44 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

When system.enableCrossNamespaceCommands is enabled (on by default), the Temporal server permits certain workflow task commands (e.g. StartChildWorkflowExecution, SignalExternalWorkflowExecution, RequestCancelExternalWorkflowExecution) to target a different namespace than the namespace authorized at the gRPC boundary. The frontend authorizes RespondWorkflowTaskCompleted based on the outer request namespace, but the history service later resolves and executes the command using the namespace embedded in command attributes without authorizing the caller for that target namespace. This can allow a worker authorized for one namespace to create, signal, or cancel workflows in another namespace. This issue affects Temporal: through 1.29.1. Fixed in 1.27.4, 1.28.2, 1.29.2.

Published by the source

30 Dec 2025, 21:30 UTC

Last modified by the source

2 Jan 2026, 15:46 UTC

Source last checked

26 Oct 2026, 15:14 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-hmhp-gh8m-c8xp

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-14987

Advisory: Temporal has an Incorrect Authorization vulnerability
IDs: CVE-2025-14987, GHSA-hmhp-gh8m-c8xp
Record: https://patchnext.com/advisories/cve-2025-14987 (revision 1, source checked 26 Oct 2026, 15:14 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: go.temporal.io/server 1.29.2, 1.29.0-135.0.0.20251218190115-b292a32bacdf, 1.28.2, 1.27.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go go.temporal.io/server: affected < 1.27.4; >= 1.28.0, < 1.28.2; >= 1.29.0, < 1.29.2; >= 1.29.0-0, < 1.29.0-135.0.0.20251218190115-b292a32bacdf; fixed in 1.29.0-135.0.0.20251218190115-b292a32bacdf, 1.29.2, 1.27.4, 1.28.2

## Suggested inspection (read-only)
- Go go.temporal.io/server: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on go.temporal.io/server.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-hmhp-gh8m-c8xp (GitHub-reviewed advisory GHSA-hmhp-gh8m-c8xp lists affected ranges: Go go.temporal.io/server >=0 =1.28.0 =1.29.0 =1.29.0-0 <1.29.0-135.0.0.20251218190115-b292a32bacdf)

Commands are suggestions: review each one before running it.