CVE-2024-58375: OpenTofu potential leaking of secret variable values when using static evaluation in v1.8

CVE-2024-58375 · Severity: high · CVSS 7.5 · Published 2026-08-16

OpenTofu versions 1.8.0 through 1.8.2 do not properly restrict sensitive variables and locals when users have opted into static evaluation of module sources, versions, and backend configurations. As a result, values marked as sensitive may be exposed through these configuration elements instead of producing an error. This is fixed in OpenTofu 1.8.3, which adds explicit errors to prevent the use of sensitive values in these contexts.

Technologies: github.com/opentofu/opentofu (Go). Vendors: Go.

Quick answers

Is CVE-2024-58375 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2024-58375 being exploited in the wild.
How severe is CVE-2024-58375?
High severity, with a CVSS score of 7.5, published 16 August 2026.
Which products and versions are affected?
github.com/opentofu/opentofu (Go) SEMVER:introduced=1.8.0,fixed=1.8.3.
Is there a fix for CVE-2024-58375?
Yes. github.com/opentofu/opentofu (Go): upgrade to 1.8.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2024-58375?
Check whether you run github.com/opentofu/opentofu (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/opentofu/opentofu (Go): upgrade to 1.8.3 or later
    go get github.com/opentofu/opentofu@v1.8.3

Affected products

  • github.com/opentofu/opentofu (Go) SEMVER:introduced=1.8.0,fixed=1.8.3

Identifiers

  • CVE-2024-58375
  • GHSA-wpr2-j6gr-pjw9
  • GO-2024-3182

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.