CVE-2026-130092
Received Received - Intake

Memory Exhaustion in Temporal Proxy via gRPC Method Names

Vulnerability report for CVE-2026-130092, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-18

Last updated on: 2026-11-18

Assigner: Temporal Technologies Inc.

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-18
Last Modified
2026-11-18
Generated
2026-11-19
AI Q&A
2026-11-19
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
temporal temporal-proxy From 0.1.0-alpha.20260716 (inc) to 1.2.0 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-770 The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability allows an attacker to cause a denial-of-service by sending gRPC requests with many distinct method names to the temporal-proxy server. The proxy records each method name as a metric label, causing unbounded memory growth until the process crashes. The issue affects versions 0.1.0-alpha.20260716 through 1.2.0.

Detection Guidance

Monitor temporal-proxy metrics for unbounded growth in metric series, particularly those labeled by method names or metadata. Check for processes consuming excessive memory due to metric label growth. Use Prometheus queries to detect series with high cardinality or labels containing many distinct values.

Impact Analysis

An attacker could exploit this to exhaust server memory, leading to crashes or degraded performance. This disrupts service availability for all users relying on the temporal-proxy. Systems using vulnerable versions are at risk of unplanned downtime.

Compliance Impact

The vulnerability could indirectly impact compliance with GDPR and HIPAA by enabling denial-of-service conditions through unbounded memory growth. GDPR requires systems to ensure availability of services, while HIPAA mandates safeguards against disruptions. Uncontrolled memory exhaustion could violate these requirements by degrading or terminating services.

Mitigation Strategies

Upgrade temporal-proxy to a fixed version (1.0.2, 1.1.2, 1.2.1, or later). If using an affected version, apply the backported fixes from PRs #288, #289, #290, or #291. Restrict network access to the temporal-proxy gRPC listener to trusted sources only.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-130092. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...