# CVE-2026-27640: tfplan2md has Sensitive Value Exposure in Generated Reports

> Attackers can view sensitive values in generated Markdown reports because tfplan2md fails to mask them correctly.

- **Severity:** High 8.5 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Feb 2026
- **Updated:** 25 Feb 2026
- **Also known as:** GHSA-5j8r-g94q-2f39

## What is CVE-2026-27640?

CVE-2026-27640 is a high-severity vulnerability in oocx tfplan2md, published on 25 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-212 (Improper Removal of Sensitive Information Before Storage or Transfer)

## Which versions are affected by CVE-2026-27640?

It affects 1 product.


Products: Oocx Tfplan2md.

## How do I fix CVE-2026-27640?

No fix has been published for CVE-2026-27640 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-27640 being exploited?

There is no known exploitation of CVE-2026-27640 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-27640 and fix it if it is affected.

What it is: CVE-2026-27640 is a high-severity vulnerability in oocx tfplan2md, published on 25 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-27640 in the wild and no public exploit code.

Affected product: oocx tfplan2md. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2026-27640/ (Markdown: https://insights.sbomify.com/CVE-2026-27640/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-27640
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-27640
- OSV: https://osv.dev/vulnerability/CVE-2026-27640

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-27640/
Summaries are generated and may contain mistakes; the official description above is the record.