MediumGHSA-hmhp-gh8m-c8xpCVE-2025-14987GO-2026-4273

Temporal has an Incorrect Authorization vulnerability

Published 30 Dec 2025 · Updated 3 Feb 2026

Is your project on an affected go.temporal.io/server?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
<1.27.4
Fixed in
1.27.4
Update to the fixed version for your release line, for example:go get go.temporal.io/server@v1.27.4
Affected
>=1.28.0 <1.28.2
Fixed in
1.28.2
Update to the fixed version for your release line, for example:go get go.temporal.io/server@v1.28.2
Affected
>=1.29.0 <1.29.2
Fixed in
1.29.2
Update to the fixed version for your release line, for example:go get go.temporal.io/server@v1.29.2
Affected
>=1.29.0-0 <1.29.0-135.0.0.20251218190115-b292a32bacdf
Fixed in
1.29.0-135.0.0.20251218190115-b292a32bacdf
Update to the fixed version for your release line, for example:go get go.temporal.io/server@v1.29.0-135.0.0.20251218190115-b292a32bacdf

Details

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.

Is GHSA-hmhp-gh8m-c8xp in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected go.temporal.io/server, and gives you the command that fixes it.

More advisories for go.temporal.io/server

  • LowCVE-2026-5199Temporal Server: attacker-controlled namespace could signal, delete, and reset workflows or activities in a victim namespace on the same cluster in go.temporal.io/server · 25 Jun 2026
  • LowCVE-2026-5724Temporal does not enforce authentication and authorization for the streaming AdminService/StreamWorkflowReplicationMessages endpoint in go.temporal.io/server · 25 Jun 2026
  • MediumCVE-2026-5724Temporal does not enforce authentication and authorization for the streaming AdminService/StreamWorkflowReplicationMessages endpoint · 10 Apr 2026
  • LowCVE-2026-5199Temporal Server: attacker-controlled namespace could signal, delete, and reset workflows or activities in a victim namespace on the same cluster · 1 Apr 2026
  • LowCVE-2025-14986Temporal has a namespace policy bypass allowing requests to be authorized for incorrect contexts in go.temporal.io/server · 12 Jan 2026
  • LowCVE-2025-14986Temporal has a namespace policy bypass allowing requests to be authorized for incorrect contexts · 30 Dec 2025
All 12 advisories for go.temporal.io/server

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.