CVE-2026-27640: oocx tfplan2md · Improper Removal of Sensitive Information Before Storage or Transfer
Affects oocx tfplan2mdSource CVE Database V5
Not known to be exploited · CVSS 8.5 High : upgrade to 1.26.1 soon.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.26.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:HExploitation evidence
Disclosed: evidence found.
CVE published 25 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade tfplan2md and oocx/tfplan2md to 1.26.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| oocxtfplan2md | Affected
| Fixed in
|
GitHuboocx/tfplan2mdpkg:github/oocx/tfplan2mdOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2026-27640, organizations should immediately upgrade tfplan2md to version 1.26.1 or later, where the vulnerability is fixed. Since no workarounds exist, patching is the only effective remediation. Additionally, organizations should audit existing Markdown reports generated by vulnerable versions to identify any inadvertent exposure of sensitive data and take appropriate steps to secure or remove such reports. Implement strict access controls and encryption for storage and transmission of Terraform plan reports to minimize risk of data leakage. Review and enhance sensitivity detection policies within Terraform configurations to reduce the amount of sensitive data included in plan files. Integrate automated scanning tools to detect sensitive data exposure in generated reports as part of CI/CD pipelines. Educate DevOps and security teams about the risks of sharing unmasked Terraform reports and enforce policies to avoid distributing reports generated by vulnerable tfplan2md versions. Monitor for any emerging exploits or indicators of compromise related to this vulnerability and respond accordingly.
Description
tfplan2md is software for converting Terraform plan JSON files into human-readable Markdown reports. Prior to version 1.26.1, a bug in tfplan2md affected several distinct rendering paths: AzApi resource body properties, AzureDevOps variable groups, Scriban template context variables, and hierarchical sensitivity detection. This caused reports to render values that should have been masked as "(sensitive)" instead. This issue is fixed in v1.26.1. No known workarounds are available.