CVE-2025-1243: Field in api-go proxy not transformed before version 1.44.1
Temporal Technologies, Inc. · api-go library
Fixed in 1.44.1 · Affected: Temporal Technologies, Inc. api-go library before 1.44.1 · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 0% of scored CVEs
DescriptionCVE.org
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 products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Temporal Technologies, Inc. · api-go librarybefore 1.44.1
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Published
- February 2025
CoverageNo articles yet
No CyberSIXT article names CVE-2025-1243 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.