Sensitive value exposure via static evaluation
Published Aug 16, 2026 · Updated Aug 16, 2026
Sensitive value exposure in OpenTofu 1.8.0 through 1.8.2 allows attackers to read secrets via static evaluation of module and backend settings. The static-evaluation logic for module source strings, module versions, and backend configuration accepts values marked sensitive and resolves them into configuration fields instead of rejecting them with an error. Exposure requires opting into static evaluation and giving an attacker a path to influence those inputs, but the consequence is limited to disclosure of the referenced sensitive values.
Summary
What happened
Sensitive value exposure in OpenTofu 1.8.0 through 1.8.2 allows attackers to read secrets via static evaluation of module and backend settings. The static-evaluation logic for module source strings, module versions, and backend configuration accepts values marked sensitive and resolves them into configuration fields instead of rejecting them with an error. Exposure requires opting into static evaluation and giving an attacker a path to influence those inputs, but the consequence is limited to disclosure of the referenced sensitive values.
The record
- CVE
- CVE-2024-58375
- Published
- Aug 16, 2026
- Updated
- Aug 16, 2026
- Vendor
- OpenTofu
- Product
- OpenTofu
- Classifications
- CWE-497
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 16, 2026CVE publishedPublication date reported by the CVE source.
- Aug 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.8.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo