CVE-2024-58375

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-16. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

August 16, 2026

Last Modified

August 17, 2026

Advisory Details (2)

Auto-updated Aug 16, 2026
Patch available. Sources: github.
generic

OpenTofu before 1.8.3 Secret Variable Leaking via Static Evaluation | Advisories | VulnCheck

https://www.vulncheck.com/advisories/opentofu-before-secret-variable-leaking-via-static-evaluation
github Patch Available

Potential leaking of secret variable values when using static evaluation in v1.8 · Advisory · opentofu/opentofu · GitHub

https://github.com/opentofu/opentofu/security/advisories/GHSA-wpr2-j6gr-pjw9

Vendor Advisories for CVE-2024-58375(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/opentofu/opentofu—1.8.3—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 25× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 06:30 UTCEG score recompute
  2. 2026-08-21 06:30 UTCGHSA enrichment
  3. 2026-08-20 22:54 UTCEPSS rescore
  4. 2026-08-20 18:26 UTCGHSA enrichment
  5. 2026-08-20 06:24 UTCGHSA enrichment
  6. 2026-08-19 18:21 UTCEG score recompute
  7. 2026-08-19 18:21 UTCGHSA enrichment
  8. 2026-08-19 17:02 UTCEPSS rescore
  9. 2026-08-19 05:05 UTCGHSA enrichment
  10. 2026-08-18 16:59 UTCEG score recompute
  11. 2026-08-18 16:59 UTCGHSA enrichment
  12. 2026-08-18 13:47 UTCEPSS rescore
  13. 2026-08-18 04:27 UTCGHSA enrichment
  14. 2026-08-17 16:24 UTCEG score recompute
  15. 2026-08-17 16:24 UTCGHSA enrichment
  16. 2026-08-17 16:11 UTCEG score recompute
  17. 2026-08-17 16:11 UTCGHSA enrichment
  18. 2026-08-17 14:42 UTCEG score recompute
  19. 2026-08-17 14:42 UTCGHSA enrichment
  20. 2026-08-17 13:45 UTCEPSS rescore
  21. 2026-08-17 02:39 UTCEG score recompute
  22. 2026-08-17 02:39 UTCGHSA enrichment
  23. 2026-08-16 14:36 UTCEG score recompute
  24. 2026-08-16 13:27 UTCEG score recompute
  25. 2026-08-16 13:26 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2024-58375?
CVE-2024-58375 is a high vulnerability published on August 16, 2026. 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…
When was CVE-2024-58375 disclosed?
CVE-2024-58375 was first published in the National Vulnerability Database on August 16, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-58375 actively exploited?
CVE-2024-58375 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 82.7% of all scored CVEs.
What is the CVSS score of CVE-2024-58375?
CVE-2024-58375 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2024-58375?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-58375, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-58375

Explore →

Is Your Infrastructure Affected by CVE-2024-58375?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs