{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-108126 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-108126 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-108126 is a medium-severity missing authorization vulnerability in temporal-proxy, published on 15 Oct 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-108126 and fix it if it is affected.\n\nWhat it is: CVE-2026-108126 is a medium-severity missing authorization vulnerability in temporal-proxy, published on 15 Oct 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-108126 in the wild and no public exploit code.\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-108126/ (Markdown: https://insights.sbomify.com/CVE-2026-108126/index.md)","id":"CVE-2026-108126","markdown":"https://insights.sbomify.com/CVE-2026-108126/index.md","name":"CVE-2026-108126","record":{"aliases":["GHSA-vm4x-rqwp-c27m"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Temporal proxy","requires_auth":"low_privilege","summary":"Attackers with access to one namespace can decrypt payloads from another namespace via the temporal-proxy, leading to unauthorized data disclosure.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Temporal","cpe":[],"cvss":{"score":6,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"temporal-proxy 0.2.0 through 0.8.0 does not bind encrypted payloads to the namespace they were encrypted for. When payload encryption is enabled, the proxy chooses the decryption key by an identifier stored in the payload rather than by the namespace of the request, and nothing in the ciphertext records that namespace. A caller whom the proxy authorizes only for namespace B, and who has obtained an encrypted payload from namespace A, can therefore have the proxy decrypt it. In 0.8.0, the caller can submit the payload to the codec server's /decode endpoint. In every affected version, a caller who can also write to namespace B on the Temporal server directly can place the payload there and read it back through the proxy. This holds whether namespaces share the default key or each has its own, because a single proxy holds every key it is configured with. The issue does not give the attacker encrypted payloads they could not already obtain, and does not allow encrypted payloads to be modified.","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 payload decryption is not bound to the request namespace","id":"CVE-2026-108126","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":9,"next":{"headline":"Role: DNS Server Information Disclosure Vulnerability","id":"CVE-2026-108127"},"packages":[],"prev":{"headline":"WordPress Post Author Authenticated SQLi","id":"CVE-2026-108125"},"products":["temporal-proxy"],"published":"2026-10-15","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-10-16","vendors":["Temporal Technologies, Inc."]},"summary":"Attackers with access to one namespace can decrypt payloads from another namespace via the temporal-proxy, leading to unauthorized data disclosure.","url":"https://insights.sbomify.com/CVE-2026-108126/"}