{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-130092 in the wild and no public exploit code.","exposure":"An affected version is exposed as installed. No special setting or call is needed.","fix":"No fix has been published for CVE-2026-130092 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-130092 is a high-severity denial of service vulnerability in temporal-proxy, published on 18 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-130092 and fix it if it is affected.\n\nWhat it is: CVE-2026-130092 is a high-severity denial of service vulnerability in temporal-proxy, published on 18 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-130092 in the wild and no public exploit code.\nExposure: An affected version is exposed as installed. No special setting or call is needed.\n\nAffected product: temporal-proxy. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-130092/ (Markdown: https://insights.sbomify.com/CVE-2026-130092/index.md)","id":"CVE-2026-130092","markdown":"https://insights.sbomify.com/CVE-2026-130092/index.md","name":"CVE-2026-130092","record":{"aliases":["GHSA-8ph7-rpwq-6342"],"analysis":{"component_type":"server_software","exploitable_when_present":false,"fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"workflow proxy","requires_auth":"none","requires_specific_call":false,"summary":"Unauthenticated callers can exhaust temporal-proxy memory by sending requests with many distinct gRPC method names, crashing the proxy.","user_interaction":"not_required","vuln_class":"denial_of_service","vulnerable_functions":[]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"Temporal","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Unauthenticated callers can exhaust temporal-proxy memory through unbounded request metrics","id":"CVE-2026-130092","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":13,"n_vendor_status":0,"next":{"headline":"AI Puffer \u003c= 2.5.28 - Unauthenticated Stored Cross-Site Scripting via AI-Generated Comment Replies","id":"CVE-2026-130121"},"nickname":null,"packages":[],"prev":{"headline":"temporal-proxy can be terminated by memory exhaustion when decompressing stored payloads","id":"CVE-2026-130091"},"products":["temporal-proxy"],"published":"2026-11-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-11-18","vendor_status":[],"vendors":["Temporal Technologies, Inc."]},"summary":"Unauthenticated callers can exhaust temporal-proxy memory by sending requests with many distinct gRPC method names, crashing the proxy.","url":"https://insights.sbomify.com/CVE-2026-130092/"}