# CVE-2025-1243: Field in api-go proxy not transformed before version 1.44.1 > Attackers can read unencrypted update response data in gRPC proxies using the Temporal api-go library, bypassing Data Converter encryption. - **Severity:** Low 2.0 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 12 Feb 2025 - **Updated:** 12 Feb 2025 - **Also known as:** GHSA-q9w6-cwj4-gf4p, GO-2025-3462 ## What is CVE-2025-1243? CVE-2025-1243 is a low-severity vulnerability in Temporal Technologies, Inc. api-go library, published on 12 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description 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. Weakness: CWE-311 (Missing Encryption of Sensitive Data) ## Which versions are affected by CVE-2025-1243? 3 open source packages ship an affected version, including go.temporal.io/api. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `go.temporal.io/api` | Go | All versions | 1.44.1 | | `go.temporal.io/api` | Go | All versions | 1.44.1 | | `go.temporal.io/api` | Go | All versions | 1.44.1 | ## How do I fix CVE-2025-1243? Upgrade go.temporal.io/api to 1.44.1 or later. ## Is CVE-2025-1243 being exploited? There is no known exploitation of CVE-2025-1243 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-1243 and fix it if it is affected. What it is: CVE-2025-1243 is a low-severity vulnerability in Temporal Technologies, Inc. api-go library, published on 12 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-1243 in the wild and no public exploit code. Affected packages and fixed versions: - go.temporal.io/api (Go): affected all versions; fixed in 1.44.1 - go.temporal.io/api (Go): affected all versions; fixed in 1.44.1 - go.temporal.io/api (Go): affected all versions; fixed in 1.44.1 Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-1243/ (Markdown: https://insights.sbomify.com/CVE-2025-1243/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-1243 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-1243 - OSV: https://osv.dev/vulnerability/CVE-2025-1243 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-1243/ Summaries are generated and may contain mistakes; the official description above is the record.