{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-130091 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-130091 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-130091 is a high-severity denial of service vulnerability in temporal-proxy, published on 18 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-130091 and fix it if it is affected.\n\nWhat it is: CVE-2026-130091 is a high-severity denial of service vulnerability in temporal-proxy, published on 18 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-130091 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-130091/ (Markdown: https://insights.sbomify.com/CVE-2026-130091/index.md)","id":"CVE-2026-130091","markdown":"https://insights.sbomify.com/CVE-2026-130091/index.md","name":"CVE-2026-130091","record":{"aliases":["GHSA-mhcr-64cf-9g9r"],"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":"low_privilege","requires_specific_call":false,"summary":"A namespace caller can store highly compressed payloads that exhaust memory and crash temporal-proxy on later reads; Temporal operators should care.","user_interaction":"not_required","vuln_class":"denial_of_service","vulnerable_functions":[]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"Temporal","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-409","name":"Improper Handling of Highly Compressed Data (Data Amplification)"}],"description":"A caller with write permission in a namespace can terminate temporal-proxy through memory exhaustion by storing highly compressed payloads in Workflow history, and the stored history causes the same failure on every later read. temporal-proxy 1.2.0 decompresses every payload marked as compressed in the responses it forwards, whether or not compression is configured. Each payload is limited to 4 MiB after decompression, but the total for a response is not, and the decoded payloads are held in memory together. The caller can store many small, highly compressed payloads through the proxy or directly at the upstream Temporal service. When that history is read through the proxy, for example by a Worker processing a task, the proxy can run out of memory and be terminated. The codec server's /decode endpoint is affected in the same way when it is enabled. Only temporal-proxy 1.2.0 is affected; earlier versions do not decompress payloads. The issue is fixed in 1.2.1. Upgrade to 1.2.1 or later.","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":"temporal-proxy can be terminated by memory exhaustion when decompressing stored payloads","id":"CVE-2026-130091","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":7,"n_vendor_status":0,"next":{"headline":"Unauthenticated callers can exhaust temporal-proxy memory through unbounded request metrics","id":"CVE-2026-130092"},"nickname":null,"packages":[],"prev":{"headline":"temporal-proxy can send a request under another upstream's credential when templated upstreams render the same address","id":"CVE-2026-130090"},"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-11-18","vendor_status":[],"vendors":["Temporal Technologies, Inc."]},"summary":"A namespace caller can store highly compressed payloads that exhaust memory and crash temporal-proxy on later reads; Temporal operators should care.","url":"https://insights.sbomify.com/CVE-2026-130091/"}