CVE-2025-1243: Field in api-go proxy not transformed before version 1.44.1
The Temporal api-go library prior to version 1.44.1 did not send update response information to Data Converter when the proxy package within the api-go module was used in a gRPC proxy prior to transmission. This resulted in information contained within the update response field not having Data Converter transformations (e.g. encryption) applied. This is an issue only when using the UpdateWorkflowExecution APIs (released on 13th January 2025) with a proxy leveraging the api-go library before version 1.44.1.
Other data fields were correctly sent to Data Converter. This issue does not impact the Data Converter server. Data was encrypted in transit. Temporal Cloud services are not impacted.
Affected Software
Remediation
Information
Event History
Frequently Asked Questions
What is the severity of CVE-2025-1243?
CVE-2025-1243 is classified as a moderate severity vulnerability due to information leakage risks.
How do I fix CVE-2025-1243?
To fix CVE-2025-1243, upgrade from the Temporal api-go library version prior to 1.44.1 to version 1.44.1 or later.
What impact does CVE-2025-1243 have on my application?
CVE-2025-1243 can lead to potential information leakage through the unhandled `update response` data if the proxy package is used improperly.
Is CVE-2025-1243 a common vulnerability?
CVE-2025-1243 affects users of the Temporal api-go library, particularly those utilizing gRPC proxies.
Where can I find more information about CVE-2025-1243?
More details about CVE-2025-1243 can be found in the release notes for the Temporal api-go library version 1.44.1.