Approved changes feed: RSS · Atom

cpe:2.3:a:temporal_technologies,_inc.:temporal-proxy:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorTemporal Technologies, Inc. (36426747-6f4f-53f1-8665-a7c798e9bdc6)
ProductTemporal Proxy (07642a0a-2639-5a7a-8479-cd15fdca6f13)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*

Notes

Imported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-108126 vulnerable 2026-11-03 10:18:00.273303 temporal-proxy payload decryption is not bound to the request namespace
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.
Published: 2026-10-15T19:09:30.743Z
Updated: 2026-10-16T15:20:20.801Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.

Inspect record JSON

Open JSON directly

Open this panel to browse, search, copy or download the JSON record.