cve.bz

CVE-2026-128079 envd: Host file disclosure through requirements path traversal and TOCTOU

6.8 mediumFix available

Medium (6.8) in tensorchord envd. Fixed in envd 1.3.6.

On this page
envd provides reproducible development environments for humans and agents. In versions starting with 0.3.38 and before 1.3.6, insufficient containment of host-side requirements-file reads in  install.python_packages(requirements=...)  could allow access to files outside the build context. An attacker able to influence build input could cause file contents interpreted as dependency entries to appear in debug logs or build-step metadata, subject to the envd process’s permissions. Exploitation in version 1.3.5 additionally requires concurrent modification of relevant filesystem paths. This issue is fixed in version 1.3.6.

Severity

CVSS 4.0

6.8 medium
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
CWEs
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition
OWASP Top 10
A01:2025 Broken Access Control
Published
Assigned by
GitHub_M (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-128079 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-128079?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-128079?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-128079 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.

Badge for a README or a site

CVE-2026-128079

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-128079](https://cve.bz/cve/badge/CVE-2026-128079.svg)](https://cve.bz/cve/CVE-2026-128079)

HTML:

<a href="https://cve.bz/cve/CVE-2026-128079"><img src="https://cve.bz/cve/badge/CVE-2026-128079.svg" alt="CVE-2026-128079"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
tensorchord envd>= 0.3.38, < 1.3.6

Fix and patched versions

  • envd (PyPI): fixed in 1.3.6

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-jv6m-48w5-5rprPyPIenvd>=0.3.38 <1.3.61.3.6

Attack patterns (CAPEC)

  • CAPEC-27 Leveraging Race Conditions via Symbolic Links Likelihood: Medium · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High
  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON