# CVE-2026-87993: Consul-template vulnerable to an information disclosure issue in error handling


- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 10 Sep 2026
- **Updated:** 10 Sep 2026
- **Also known as:** BIT-consul-2026-87993, GHSA-h4cr-56m4-rqc8

## What is CVE-2026-87993?

CVE-2026-87993 is a high-severity vulnerability in HashiCorp Tooling, published on 10 Sep 2026. 

### Official description

The consul-template library is vulnerable to an information disclosure issue in its error handling path that may allow Vault secret values to appear in template error messages, log output, and downstream surfaces such as Nomad task events. This vulnerability (CVE-2026-87993) is fixed in consul-template 0.43.0.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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

1 open source package ship an affected version, including consul.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `consul` | Bitnami | From 0.27.2 | 0.43.0 |

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

Upgrade consul to 0.43.0 or later.

## Is CVE-2026-87993 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-87993 is a high-severity vulnerability in HashiCorp Tooling, published on 10 Sep 2026. 
Exploitation: There is no known exploitation of CVE-2026-87993 in the wild and no public exploit code.

Affected packages and fixed versions:
- consul (Bitnami): affected from 0.27.2; fixed in 0.43.0

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

## Sources

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

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