Temporal Server vulnerable to Incorrect Authorization and Insecure Default Initialization of Resource

Exploitation

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

CVSS

3.0 · CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:L

EPSS

• CVE-2023-3485: 0.17% estimated exploitation activity in the next 30 days; percentile 5.92 (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.

Insecure defaults in open-source Temporal Server before version 1.20 on all platforms allows an attacker to craft a task token with access to a namespace other than the one specified in the request. Creation of this task token must be done outside of the normal Temporal server flow. It requires the namespace UUID and information from the workflow history for the target namespace. Under these conditions, it is possible to interfere with pending tasks in other namespaces, such as marking a task failed or completed. If a task is targeted for completion by the attacker, the targeted namespace must also be using the same data converter configuration as the initial, valid, namespace for the task completion payload to be decoded by workers in the target namespace.

Published by the source

30 Jun 2023, 18:31 UTC

Last modified by the source

5 Nov 2023, 05:06 UTC

Source last checked

26 Oct 2026, 14:59 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-gm2g-2xr9-pxxj

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

# Patch Next advisory brief: CVE-2023-3485

Advisory: Temporal Server vulnerable to Incorrect Authorization and Insecure Default Initialization of Resource
IDs: CVE-2023-3485, GHSA-gm2g-2xr9-pxxj
Record: https://patchnext.com/advisories/cve-2023-3485 (revision 1, source checked 26 Oct 2026, 14:59 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.0)
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.20.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go go.temporal.io/server: affected < 1.20.0; fixed in 1.20.0

## 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-gm2g-2xr9-pxxj (GitHub-reviewed advisory GHSA-gm2g-2xr9-pxxj lists affected ranges: Go go.temporal.io/server >=0 <1.20.0)

Commands are suggestions: review each one before running it.