CVE-2022-38149 is a high-severity (CVSS 7.5) CWE-532 vulnerability in github.com/hashicorp/consul-template. A fix is available for github.com/hashicorp/consul-template — see the affected versions and patch details below.
HashiCorp Consul Template could reveal Vault secret contents in error messages
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/hashicorp/consul-template🐹github.com/hashicorp/consul-template🐹github.com/hashicorp/consul-templateReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
In HashiCorp Consul Template through version 0.29.1, invalid templates could inadvertently reveal the contents of Vault secret in errors returned by the *template.Template.Execute 5 method, when given a template using Vault secret contents incorrectly. This method has been updated to redact Vault secrets when creating an error string, making it safe to log the error.. This issue was fixed in version 0.29.2.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/hashicorp/consul-template | all versions | 0.27.3go get github.com/hashicorp/consul-template@v0.27.3 |
| 🐹Go | github.com/hashicorp/consul-template | ≥ 0.28.0&&< 0.28.3 | 0.28.3go get github.com/hashicorp/consul-template@v0.28.3 |
| 🐹Go | github.com/hashicorp/consul-template | ≥ 0.29.0&&< 0.29.2 | 0.29.2go get github.com/hashicorp/consul-template@v0.29.2 |
Affected Products
consul templatehashicorpDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/hashicorp/consul-template, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/hashicorp/consul-template to 0.27.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-38149 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| RHODF-4.13-RHEL-9 | odf4/mcg-rhel9-operator:v4.13.0-41 | RHSA-2023:3742 |
Frequently Asked Questions
Is CVE-2022-38149 in your dependencies?
Find it across Go, including transitive dependencies.