CVE-2026-130090 (GCVE-0-2026-130090)
Vulnerability from cvelistv5 – Published: 2026-11-18 20:28 – Updated: 2026-11-18 21:18
VLAI
EPSS
VEX
Title
temporal-proxy can send a request under another upstream's credential when templated upstreams render the same address
Summary
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.
Severity
SSVC
Exploitation: none
Automatable: no
Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-18 21:18 UTC
CWE
- CWE-488 - Exposure of Data Element to Wrong Session
Assigner
References
9 references
Impacted products
1 product
| Vendor | Product | Version | |
|---|---|---|---|
| Temporal Technologies, Inc. | temporal-proxy |
Affected:
0.1.0 , ≤ 0.10.1
(semver)
Affected: 1.0.0 , < 1.0.2 (semver) Affected: 1.1.0 , < 1.1.2 (semver) |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-130090",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-18T21:18:05.592250Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T21:18:15.630Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"collectionURL": "https://pkg.go.dev",
"defaultStatus": "unaffected",
"packageName": "github.com/temporalio/temporal-proxy",
"product": "temporal-proxy",
"programFiles": [
"internal/proxy/resolver.go",
"internal/transport/connect/pool.go"
],
"programRoutines": [
{
"name": "DynamicResolver.Resolve"
},
{
"name": "Pool.ConnOrCreate"
}
],
"repo": "https://github.com/temporalio/temporal-proxy",
"vendor": "Temporal Technologies, Inc.",
"versions": [
{
"lessThanOrEqual": "0.10.1",
"status": "affected",
"version": "0.1.0",
"versionType": "semver"
},
{
"lessThan": "1.0.2",
"status": "affected",
"version": "1.0.0",
"versionType": "semver"
},
{
"lessThan": "1.1.2",
"status": "affected",
"version": "1.1.0",
"versionType": "semver"
}
]
}
],
"configurations": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eExploitation requires two or more templated upstreams that can render the same address and TLS server name with different outbound credentials, namespace translation, or encryption keys. It crosses an authorization boundary only where an external authenticator restricts callers to particular namespaces; otherwise any caller can already route requests to either upstream.\u003c/p\u003e"
}
],
"value": "Exploitation requires two or more templated upstreams that can render the same address and TLS server name with different outbound credentials, namespace translation, or encryption keys. It crosses an authorization boundary only where an external authenticator restricts callers to particular namespaces; otherwise any caller can already route requests to either upstream."
},
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eAttack Requirements is Present because the colliding upstream configuration, a restricting external authenticator, and a connection already opened by the other upstream\u0027s traffic are outside the caller\u0027s control. Confidentiality and integrity are Low on the proxy and on the upstream Temporal service because the caller does not choose which upstream\u0027s connection serves the request.\u003c/p\u003e"
}
],
"value": "Attack Requirements is Present because the colliding upstream configuration, a restricting external authenticator, and a connection already opened by the other upstream\u0027s traffic are outside the caller\u0027s control. Confidentiality and integrity are Low on the proxy and on the upstream Temporal service because the caller does not choose which upstream\u0027s connection serves the request."
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eWhen two templated upstreams in temporal-proxy render the same address, a request routed to one upstream can be sent under the other upstream\u0027s 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\u0027s 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\u0027s 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\u0027 ordinary traffic, and a caller that an external authenticator restricts to one upstream\u0027s namespaces can use it to act under the other upstream\u0027s 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.\u003c/p\u003e"
}
],
"value": "When two templated upstreams in temporal-proxy render the same address, a request routed to one upstream can be sent under the other upstream\u0027s 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\u0027s 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\u0027s 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\u0027 ordinary traffic, and a caller that an external authenticator restricts to one upstream\u0027s namespaces can use it to act under the other upstream\u0027s 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."
}
],
"impacts": [
{
"descriptions": [
{
"lang": "en",
"value": "Requests routed to one upstream can be authorized at the Temporal server under another upstream\u0027s credential, and their payloads encrypted or decrypted under that upstream\u0027s keys. The caller does not choose which upstream\u0027s connection is used and does not obtain the credential. No availability impact was identified."
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "PRESENT",
"attackVector": "NETWORK",
"baseScore": 2.3,
"baseSeverity": "LOW",
"exploitMaturity": "NOT_DEFINED",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "LOW",
"subIntegrityImpact": "LOW",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "LOW",
"vulnIntegrityImpact": "LOW",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-488",
"description": "CWE-488: Exposure of Data Element to Wrong Session",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T20:28:53.871Z",
"orgId": "61241ed8-fa44-4f23-92db-b8c443751968",
"shortName": "Temporal"
},
"references": [
{
"name": "Fix pull request",
"tags": [
"patch"
],
"url": "https://github.com/temporalio/temporal-proxy/pull/279"
},
{
"name": "Fix commit",
"tags": [
"patch"
],
"url": "https://github.com/temporalio/temporal-proxy/commit/d7228fac60798e4047e00606b8b41573ab2f77c4"
},
{
"name": "Backport pull request for the 1.0 release line",
"tags": [
"patch"
],
"url": "https://github.com/temporalio/temporal-proxy/pull/286"
},
{
"name": "Backport commit on releases/v1.0.x",
"tags": [
"patch"
],
"url": "https://github.com/temporalio/temporal-proxy/commit/9d1dc1dcf92fef191e61e9076ff46fd7c8570702"
},
{
"name": "Backport pull request for the 1.1 release line",
"tags": [
"patch"
],
"url": "https://github.com/temporalio/temporal-proxy/pull/285"
},
{
"name": "Backport commit on releases/v1.1.x",
"tags": [
"patch"
],
"url": "https://github.com/temporalio/temporal-proxy/commit/d201e99150e90e34b033480f91022067f39b3c8e"
},
{
"name": "temporal-proxy 1.0.2",
"tags": [
"release-notes"
],
"url": "https://github.com/temporalio/temporal-proxy/releases/tag/v1.0.2"
},
{
"name": "temporal-proxy 1.1.2",
"tags": [
"release-notes"
],
"url": "https://github.com/temporalio/temporal-proxy/releases/tag/v1.1.2"
},
{
"name": "temporal-proxy 1.2.0",
"tags": [
"release-notes"
],
"url": "https://github.com/temporalio/temporal-proxy/releases/tag/v1.2.0"
}
],
"solutions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eUpgrade to temporal-proxy 1.2.0 or later, or to 1.0.2 or 1.1.2 on those release lines. Fixed releases scope each pooled connection to the upstream that created it. Releases before 1.0.0 receive no fix.\u003c/p\u003e"
}
],
"value": "Upgrade to temporal-proxy 1.2.0 or later, or to 1.0.2 or 1.1.2 on those release lines. Fixed releases scope each pooled connection to the upstream that created it. Releases before 1.0.0 receive no fix."
}
],
"source": {
"discovery": "INTERNAL"
},
"title": "temporal-proxy can send a request under another upstream\u0027s credential when templated upstreams render the same address",
"workarounds": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eConfigure templated upstreams so that no two can render the same address, for example by giving each hostPort template a distinct fixed suffix.\u003c/p\u003e"
}
],
"value": "Configure templated upstreams so that no two can render the same address, for example by giving each hostPort template a distinct fixed suffix."
}
]
}
},
"cveMetadata": {
"assignerOrgId": "61241ed8-fa44-4f23-92db-b8c443751968",
"assignerShortName": "Temporal",
"cveId": "CVE-2026-130090",
"datePublished": "2026-11-18T20:28:53.871Z",
"dateReserved": "2026-11-16T20:59:58.726Z",
"dateUpdated": "2026-11-18T21:18:15.630Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-130090",
"date": "2026-11-22",
"epss": "0.00453",
"percentile": "0.40141"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"collectionURL": "https://pkg.go.dev",
"defaultStatus": "unaffected",
"packageName": "github.com/temporalio/temporal-proxy",
"product": "temporal-proxy",
"programFiles": [
"internal/proxy/resolver.go",
"internal/transport/connect/pool.go"
],
"programRoutines": [
{
"name": "DynamicResolver.Resolve"
},
{
"name": "Pool.ConnOrCreate"
}
],
"repo": "https://github.com/temporalio/temporal-proxy",
"vendor": "Temporal Technologies, Inc.",
"versions": [
{
"lessThanOrEqual": "0.10.1",
"status": "affected",
"version": "0.1.0",
"versionType": "semver"
},
{
"lessThan": "1.0.2",
"status": "affected",
"version": "1.0.0",
"versionType": "semver"
},
{
"lessThan": "1.1.2",
"status": "affected",
"version": "1.1.0",
"versionType": "semver"
}
]
}
],
"source": "security@temporal.io"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "When two templated upstreams in temporal-proxy render the same address, a request routed to one upstream can be sent under the other upstream\u0027s 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\u0027s 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\u0027s 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\u0027 ordinary traffic, and a caller that an external authenticator restricts to one upstream\u0027s namespaces can use it to act under the other upstream\u0027s 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."
}
],
"id": "CVE-2026-130090",
"lastModified": "2026-11-18T22:17:18.767",
"metrics": {
"cvssMetricV40": [
{
"cvssData": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "PRESENT",
"attackVector": "NETWORK",
"availabilityRequirement": "NOT_DEFINED",
"baseScore": 2.3,
"baseSeverity": "LOW",
"confidentialityRequirement": "NOT_DEFINED",
"exploitMaturity": "NOT_DEFINED",
"integrityRequirement": "NOT_DEFINED",
"modifiedAttackComplexity": "NOT_DEFINED",
"modifiedAttackRequirements": "NOT_DEFINED",
"modifiedAttackVector": "NOT_DEFINED",
"modifiedPrivilegesRequired": "NOT_DEFINED",
"modifiedSubAvailabilityImpact": "NOT_DEFINED",
"modifiedSubConfidentialityImpact": "NOT_DEFINED",
"modifiedSubIntegrityImpact": "NOT_DEFINED",
"modifiedUserInteraction": "NOT_DEFINED",
"modifiedVulnAvailabilityImpact": "NOT_DEFINED",
"modifiedVulnConfidentialityImpact": "NOT_DEFINED",
"modifiedVulnIntegrityImpact": "NOT_DEFINED",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "LOW",
"subIntegrityImpact": "LOW",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "LOW",
"vulnIntegrityImpact": "LOW",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"source": "security@temporal.io",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-130090",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-18T21:18:05.592250Z",
"version": "2.0.3"
}
}
]
},
"published": "2026-11-18T21:17:49.150",
"references": [
{
"source": "security@temporal.io",
"url": "https://github.com/temporalio/temporal-proxy/commit/9d1dc1dcf92fef191e61e9076ff46fd7c8570702"
},
{
"source": "security@temporal.io",
"url": "https://github.com/temporalio/temporal-proxy/commit/d201e99150e90e34b033480f91022067f39b3c8e"
},
{
"source": "security@temporal.io",
"url": "https://github.com/temporalio/temporal-proxy/commit/d7228fac60798e4047e00606b8b41573ab2f77c4"
},
{
"source": "security@temporal.io",
"url": "https://github.com/temporalio/temporal-proxy/pull/279"
},
{
"source": "security@temporal.io",
"url": "https://github.com/temporalio/temporal-proxy/pull/285"
},
{
"source": "security@temporal.io",
"url": "https://github.com/temporalio/temporal-proxy/pull/286"
},
{
"source": "security@temporal.io",
"url": "https://github.com/temporalio/temporal-proxy/releases/tag/v1.0.2"
},
{
"source": "security@temporal.io",
"url": "https://github.com/temporalio/temporal-proxy/releases/tag/v1.1.2"
},
{
"source": "security@temporal.io",
"url": "https://github.com/temporalio/temporal-proxy/releases/tag/v1.2.0"
}
],
"sourceIdentifier": "security@temporal.io",
"vulnStatus": "Received",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-488"
}
],
"source": "security@temporal.io",
"type": "Secondary"
}
]
}
},
"vulnrichment": {
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-130090",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-18T21:18:05.592250Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T21:18:10.744Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"collectionURL": "https://pkg.go.dev",
"defaultStatus": "unaffected",
"packageName": "github.com/temporalio/temporal-proxy",
"product": "temporal-proxy",
"programFiles": [
"internal/proxy/resolver.go",
"internal/transport/connect/pool.go"
],
"programRoutines": [
{
"name": "DynamicResolver.Resolve"
},
{
"name": "Pool.ConnOrCreate"
}
],
"repo": "https://github.com/temporalio/temporal-proxy",
"vendor": "Temporal Technologies, Inc.",
"versions": [
{
"lessThanOrEqual": "0.10.1",
"status": "affected",
"version": "0.1.0",
"versionType": "semver"
},
{
"lessThan": "1.0.2",
"status": "affected",
"version": "1.0.0",
"versionType": "semver"
},
{
"lessThan": "1.1.2",
"status": "affected",
"version": "1.1.0",
"versionType": "semver"
}
]
}
],
"configurations": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eExploitation requires two or more templated upstreams that can render the same address and TLS server name with different outbound credentials, namespace translation, or encryption keys. It crosses an authorization boundary only where an external authenticator restricts callers to particular namespaces; otherwise any caller can already route requests to either upstream.\u003c/p\u003e"
}
],
"value": "Exploitation requires two or more templated upstreams that can render the same address and TLS server name with different outbound credentials, namespace translation, or encryption keys. It crosses an authorization boundary only where an external authenticator restricts callers to particular namespaces; otherwise any caller can already route requests to either upstream."
},
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eAttack Requirements is Present because the colliding upstream configuration, a restricting external authenticator, and a connection already opened by the other upstream\u0027s traffic are outside the caller\u0027s control. Confidentiality and integrity are Low on the proxy and on the upstream Temporal service because the caller does not choose which upstream\u0027s connection serves the request.\u003c/p\u003e"
}
],
"value": "Attack Requirements is Present because the colliding upstream configuration, a restricting external authenticator, and a connection already opened by the other upstream\u0027s traffic are outside the caller\u0027s control. Confidentiality and integrity are Low on the proxy and on the upstream Temporal service because the caller does not choose which upstream\u0027s connection serves the request."
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eWhen two templated upstreams in temporal-proxy render the same address, a request routed to one upstream can be sent under the other upstream\u0027s 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\u0027s 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\u0027s 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\u0027 ordinary traffic, and a caller that an external authenticator restricts to one upstream\u0027s namespaces can use it to act under the other upstream\u0027s 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.\u003c/p\u003e"
}
],
"value": "When two templated upstreams in temporal-proxy render the same address, a request routed to one upstream can be sent under the other upstream\u0027s 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\u0027s 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\u0027s 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\u0027 ordinary traffic, and a caller that an external authenticator restricts to one upstream\u0027s namespaces can use it to act under the other upstream\u0027s 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."
}
],
"impacts": [
{
"descriptions": [
{
"lang": "en",
"value": "Requests routed to one upstream can be authorized at the Temporal server under another upstream\u0027s credential, and their payloads encrypted or decrypted under that upstream\u0027s keys. The caller does not choose which upstream\u0027s connection is used and does not obtain the credential. No availability impact was identified."
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "PRESENT",
"attackVector": "NETWORK",
"baseScore": 2.3,
"baseSeverity": "LOW",
"exploitMaturity": "NOT_DEFINED",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "LOW",
"subIntegrityImpact": "LOW",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "LOW",
"vulnIntegrityImpact": "LOW",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-488",
"description": "CWE-488: Exposure of Data Element to Wrong Session",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T20:28:53.871Z",
"orgId": "61241ed8-fa44-4f23-92db-b8c443751968",
"shortName": "Temporal"
},
"references": [
{
"name": "Fix pull request",
"tags": [
"patch"
],
"url": "https://github.com/temporalio/temporal-proxy/pull/279"
},
{
"name": "Fix commit",
"tags": [
"patch"
],
"url": "https://github.com/temporalio/temporal-proxy/commit/d7228fac60798e4047e00606b8b41573ab2f77c4"
},
{
"name": "Backport pull request for the 1.0 release line",
"tags": [
"patch"
],
"url": "https://github.com/temporalio/temporal-proxy/pull/286"
},
{
"name": "Backport commit on releases/v1.0.x",
"tags": [
"patch"
],
"url": "https://github.com/temporalio/temporal-proxy/commit/9d1dc1dcf92fef191e61e9076ff46fd7c8570702"
},
{
"name": "Backport pull request for the 1.1 release line",
"tags": [
"patch"
],
"url": "https://github.com/temporalio/temporal-proxy/pull/285"
},
{
"name": "Backport commit on releases/v1.1.x",
"tags": [
"patch"
],
"url": "https://github.com/temporalio/temporal-proxy/commit/d201e99150e90e34b033480f91022067f39b3c8e"
},
{
"name": "temporal-proxy 1.0.2",
"tags": [
"release-notes"
],
"url": "https://github.com/temporalio/temporal-proxy/releases/tag/v1.0.2"
},
{
"name": "temporal-proxy 1.1.2",
"tags": [
"release-notes"
],
"url": "https://github.com/temporalio/temporal-proxy/releases/tag/v1.1.2"
},
{
"name": "temporal-proxy 1.2.0",
"tags": [
"release-notes"
],
"url": "https://github.com/temporalio/temporal-proxy/releases/tag/v1.2.0"
}
],
"solutions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eUpgrade to temporal-proxy 1.2.0 or later, or to 1.0.2 or 1.1.2 on those release lines. Fixed releases scope each pooled connection to the upstream that created it. Releases before 1.0.0 receive no fix.\u003c/p\u003e"
}
],
"value": "Upgrade to temporal-proxy 1.2.0 or later, or to 1.0.2 or 1.1.2 on those release lines. Fixed releases scope each pooled connection to the upstream that created it. Releases before 1.0.0 receive no fix."
}
],
"source": {
"discovery": "INTERNAL"
},
"title": "temporal-proxy can send a request under another upstream\u0027s credential when templated upstreams render the same address",
"workarounds": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eConfigure templated upstreams so that no two can render the same address, for example by giving each hostPort template a distinct fixed suffix.\u003c/p\u003e"
}
],
"value": "Configure templated upstreams so that no two can render the same address, for example by giving each hostPort template a distinct fixed suffix."
}
]
}
},
"cveMetadata": {
"assignerOrgId": "61241ed8-fa44-4f23-92db-b8c443751968",
"assignerShortName": "Temporal",
"cveId": "CVE-2026-130090",
"datePublished": "2026-11-18T20:28:53.871Z",
"dateReserved": "2026-11-16T20:59:58.726Z",
"dateUpdated": "2026-11-18T21:18:15.630Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…