The consul-template library before version 0.42.0 is vulnerable to a sandbox path bypass in the file template helper that may allow reading an out-of-sandbox file. This vulnerability (CVE-2026-5061) is fixed in consul-template 0.42.0.
Severity
CVSS 3.1
4.7 medium
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
0.2%(unchanged from 0.2% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 4th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-05-12. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-59Improper Link Resolution Before File Access (Link Following)
Show the promptExplain CVE-2026-5061 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-5061?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-5061?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-5061 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Repositories on GitHub named after this CVE. Nobody has checked them and they are not scanned: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.
0xmrma/CVE-2026-50611 star, created Consul Template validated where a symlink pointed during template evaluation, but its later dependency fetch read the original path. Retarg…
Attack patterns (CAPEC)
CAPEC-17 Using Malicious Files Likelihood: High · Severity: Very High
CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
CAPEC-132 Symlink Attack Likelihood: Low · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.