FKIE_CVE-2026-130092
Vulnerability from fkie_nvd - Published: 2026-11-18 21:17 - Updated: 2026-11-18 22:17
Severity
Summary
A caller who can reach the temporal-proxy gRPC listener, with or without a valid credential, can grow the proxy's memory until the process is terminated by sending requests with many distinct gRPC method names. temporal-proxy labels its request metrics with the method name exactly as the caller sent it, and records every request, including those that authentication or routing reject. Each distinct method name adds metric series that are never removed. The series grow whether or not the metrics endpoint is scraped, and metric labels configured from request metadata multiply the growth. temporal-proxy versions 0.1.0-alpha.20260716 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.
References
Impacted products
| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"collectionURL": "https://pkg.go.dev",
"defaultStatus": "unaffected",
"packageName": "github.com/temporalio/temporal-proxy",
"product": "temporal-proxy",
"programFiles": [
"internal/server/reporter.go",
"internal/dataplane/dataplane.go"
],
"programRoutines": [
{
"name": "Reporter.Observe"
}
],
"repo": "https://github.com/temporalio/temporal-proxy",
"vendor": "Temporal Technologies, Inc.",
"versions": [
{
"lessThanOrEqual": "0.10.1",
"status": "affected",
"version": "0.1.0-alpha.20260716",
"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"
},
{
"lessThan": "1.2.1",
"status": "affected",
"version": "1.2.0",
"versionType": "semver"
}
]
}
],
"source": "security@temporal.io"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "A caller who can reach the temporal-proxy gRPC listener, with or without a valid credential, can grow the proxy\u0027s memory until the process is terminated by sending requests with many distinct gRPC method names. temporal-proxy labels its request metrics with the method name exactly as the caller sent it, and records every request, including those that authentication or routing reject. Each distinct method name adds metric series that are never removed. The series grow whether or not the metrics endpoint is scraped, and metric labels configured from request metadata multiply the growth. temporal-proxy versions 0.1.0-alpha.20260716 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."
}
],
"id": "CVE-2026-130092",
"lastModified": "2026-11-18T22:17:19.110",
"metrics": {
"cvssMetricV40": [
{
"cvssData": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"availabilityRequirement": "NOT_DEFINED",
"baseScore": 8.7,
"baseSeverity": "HIGH",
"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": "NONE",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/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": "HIGH",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "NONE",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"source": "security@temporal.io",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-130092",
"options": [
{
"exploitation": "none"
},
{
"automatable": "yes"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-18T21:21:23.323538Z",
"version": "2.0.3"
}
}
]
},
"published": "2026-11-18T21:17:49.520",
"references": [
{
"source": "security@temporal.io",
"url": "https://github.com/temporalio/temporal-proxy/blob/v1.2.0/internal/dataplane/dataplane.go#L185-L192"
},
{
"source": "security@temporal.io",
"url": "https://github.com/temporalio/temporal-proxy/blob/v1.2.0/internal/server/reporter.go#L69-L94"
},
{
"source": "security@temporal.io",
"url": "https://github.com/temporalio/temporal-proxy/commit/4b9aba1b14d9b656c32bb3394de7ab820b33c98a"
},
{
"source": "security@temporal.io",
"url": "https://github.com/temporalio/temporal-proxy/commit/700fc2eae5196ce612eac4b7e8e25877269f6c05"
},
{
"source": "security@temporal.io",
"url": "https://github.com/temporalio/temporal-proxy/commit/87254989bf135dfaf8176e0c822d24aa86907c78"
},
{
"source": "security@temporal.io",
"url": "https://github.com/temporalio/temporal-proxy/commit/f745e71918dc386524a606eff1153dbd0f2b0091"
},
{
"source": "security@temporal.io",
"url": "https://github.com/temporalio/temporal-proxy/pull/288"
},
{
"source": "security@temporal.io",
"url": "https://github.com/temporalio/temporal-proxy/pull/289"
},
{
"source": "security@temporal.io",
"url": "https://github.com/temporalio/temporal-proxy/pull/290"
},
{
"source": "security@temporal.io",
"url": "https://github.com/temporalio/temporal-proxy/pull/291"
},
{
"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.1"
}
],
"sourceIdentifier": "security@temporal.io",
"vulnStatus": "Received",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-770"
}
],
"source": "security@temporal.io",
"type": "Secondary"
}
]
}
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…