Skip to main content
Menu
CVEs

CVE

Temporal Technologies temporal-proxy authorization bypass in upstream connection pool

CVE-2026-130090EUVD-2026-129193Published Updated Summary written by a model

2.3LowCNA
Exploited
No known exploitation
Fix
Fixed in 1.0.2, 1.1.2
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 1.0.2, 1.1.2.

Summary

temporal-proxy from Temporal Technologies, Inc. can send a request under another upstream's credential when two templated upstreams render the same address, because it pools connections by rendered address and TLS server name only. A network caller with low privileges can use this to have the Temporal service authorize requests as the other upstream's principal, and where an external authenticator limits the caller to one upstream's namespaces, to act under the other upstream's credential.

Original description

When two templated upstreams in temporal-proxy render the same address, a request routed to one upstream can be sent under the other upstream's credential, namespace translation, and payload encryption keys. temporal-proxy pools connections for templated upstreams by rendered address and TLS server name only, although each upstream's outbound credential, namespace translation, and payload encryption keys, where configured, are attached to its connection. A request routed to one upstream can therefore be sent over the connection the other created, and the upstream Temporal service authorizes it as the other upstream's principal. Configuration validation rejects only identical hostPort values, so templates that differ in text but render the same address are accepted. This mixes the two upstreams' ordinary traffic, and a caller that an external authenticator restricts to one upstream's namespaces can use it to act under the other upstream's credential. Deployments with at most one templated upstream are not affected. temporal-proxy versions 0.1.0 through 1.1.1 are affected. The issue is fixed in 1.0.2, 1.1.2, and 1.2.0, and releases before 1.0.0 receive no fix. Upgrade to the fixed release for the deployed minor release line.

cve.now Index

15Pcve.now Index 15 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach10/20Affects Go packages
  • Severity2.3/10CVSS 2.3
  • No patch0/5No signal

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active
  • Would score about 34 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 1.0.2, 1.1.2.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-130090 (temporal-proxy can send a request under another upstream's credential when templated upstreams render the same address), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130090 (entry last updated 2026-11-18):
Affected:
- Go package github.com/temporalio/temporal-proxy: from 0.1.0, through 0.10.1; from 1.0.0, fixed in 1.0.2; from 1.1.0, fixed in 1.1.2
Fixed versions: 1.0.2, 1.1.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-130090 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130090 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/temporalio/temporal-proxy/pull/279
- https://github.com/temporalio/temporal-proxy/commit/d7228fac60798e4047e00606b8b41573ab2f77c4
- https://github.com/temporalio/temporal-proxy/pull/286
- https://github.com/temporalio/temporal-proxy/commit/9d1dc1dcf92fef191e61e9076ff46fd7c8570702
- https://github.com/temporalio/temporal-proxy/pull/285
- https://github.com/temporalio/temporal-proxy/commit/d201e99150e90e34b033480f91022067f39b3c8e
- https://github.com/temporalio/temporal-proxy/releases/tag/v1.0.2
- https://github.com/temporalio/temporal-proxy/releases/tag/v1.1.2
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130090
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130090"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

Evidence 11

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130090

Is CVE-2026-130090 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-130090?

github.com/temporalio/temporal-proxy (Go): from 0.1.0 through 0.10.1; from 1.0.0 before 1.0.2; from 1.1.0 before 1.1.2.Source: cve.now feed data

How do I fix CVE-2026-130090?

Upgrade to a fixed version: 1.0.2, 1.1.2.Source: cve.now feed data

More CVEs