CVE-2026-130089: temporal-proxy request namespace can redirect a templated upstream and leak its API key

Published Nov 18, 2026
·
Updated

A caller who can send requests to the temporal-proxy gRPC listener can obtain the static API key of an upstream whose address is templated from the request namespace, and then use that key directly against the upstream Temporal service. temporal-proxy does not validate the request namespace before rendering it into a templated upstream address, so when an upstream's hostPort is templated from the namespace, as in the published Temporal Cloud configuration example, a crafted namespace changes the host the proxy dials. If that upstream verifies TLS against the system trust store and sets no literal server name, a caller-controlled host with a publicly trusted certificate passes verification and receives the key. The built-in static-token and JWKS authenticators do not restrict namespaces, so any caller they admit can do this; an external authenticator that admits only listed namespaces prevents it. temporal-proxy versions 0.1.0 through 1.2.0 are affected. The issue is fixed in 1.0.2, 1.1.2, and 1.2.1, and releases before 1.0.0 receive no fix. Upgrade to the fixed release for the deployed minor release line, and rotate any upstream API key that untrusted callers could reach.

Affected Software

1 affected component
Temporal temporal-proxy>=0.1.0<=1.0.1, >=1.1.0<=1.1.1, =1.2.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade temporal-proxy to a version that resolves this vulnerability.

    Fixed in 1.0.2
  2. Upgrade

    Upgrade temporal-proxy to a version that resolves this vulnerability.

    Fixed in 1.1.2
  3. Upgrade

    Upgrade temporal-proxy to a version that resolves this vulnerability.

    Fixed in 1.2.1
  4. Configuration

    Before upgrading, change any configuration that templates the whole host so the templated host ends in a literal domain; for example, use a literal domain suffix such as .tmprl.cloud.

    temporal-proxy hostPort or tls.serverName
  5. Compensating control

    Use an external authenticator that admits only listed namespaces; the built-in static-token and JWKS authenticators do not restrict namespaces.

  6. Operational

    Rotate any upstream API key held by an affected deployment that untrusted callers could reach.

Event History

Nov 18, 2026
CVE Published
via MITRE·08:20 PM
Data Sourced
via MITRE·08:20 PM
RemedyDescriptionWeakness
Data Sourced
via OSV·08:20 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:17 PM
DescriptionSeverityWeakness

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203