ENVD · CVE-2026-128079 · Package
FIX → 1.3.6
envd reads requirements files on the host during builds, and a path traversal plus a race between symlink check and file open lets a build input read files outside its build context. Contents interpreted as dependency entries can appear in build logs and build-step metadata.
first public Nov 13, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams that use envd to build sandboxes and pass requirements file paths into install.python_packages, especially where the build input can be influenced by someone outside the team. The risk depends on the envd process having read access to the files, and the advisory notes the race needs concurrent filesystem changes. Teams that do not use the Python package install helper with requirements paths can likely skip it.
Not affected if no-untrusted-build-input, not-using-python-packages-requirements
Who cares envd, python, sandbox-builds
pip show envd and compare it to the affected range (>= 0.3.38, < 1.3.6).install.python_packages(requirements=...) calls in build definitions that take paths from untrusted input.Upgrade to 1.3.6
envd 1.3.6 (fixed version per the product data; v1.3.5 is still affected by the TOCTOU variant)envd’s install.python_packages(requirements=...) could read files outside the build context on the host. Content interpreted as dependency entries could appear in build logs and build-step metadata.
Commit f576c92, released in v1.3.5, added path containment validation but left a time-of-check/time-of-use (TOCTOU) race between symlink resolution and opening the requirements file. Commit 9d575b3 addresses this race by opening requirements files through a directory-rooted filesystem handle.
envd reads requirements files on the host to determine whether their contents can be embedded directly into a pip installation build step.
The vulnerable host-side requirements read was introduced in v0.3.38. Version v1.3.5 added containment checks for static path escapes but remained vulnerable to a TOCTOU race. The complete fix is included in v1.3.6.
Before f576c92, this host read lacked a build-context containment check. That commit added frontend path validation and a compile-time check using filepath.EvalSymlinks followed by a containment comparison.
However, symlink resolution returns a pathname rather than a pinned filesystem object. The subsequent os.Open independently resolves that pathname. Concurrent filesystem changes could therefore invalidate the containment check before the file was opened.
The complete fix uses os.OpenRoot and Root.Open to enforce containment during filesystem traversal.
Resources:
The security-relevant condition is a requirements-file pathname whose filesystem resolution changes between validation and opening. The containment check describes the filesystem at validation time, while the later pathname-based open may access a different object.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
The fix includes a deterministic regression test for the underlying object-pinning guarantee. It opens a context directory handle, moves that directory, and creates a replacement directory at the original pathname containing different requirements. The rooted reader continues reading the original context; a pathname-based reader reads the replacement.
This regression test demonstrates the distinction between rooted and pathname-based reads. It is not an end-to-end demonstration of host file disclosure.
An attacker who can influence the build input—and, for the residual race in v1.3.5, concurrently modify the relevant filesystem paths—may cause envd to read files outside the intended build context, subject to the permissions of the envd process.
Depending on the file contents and requirements parsing, information may be exposed through dependency debug logs and build-step metadata. This issue does not establish arbitrary code execution or unrestricted disclosure of every file.
v1.3.5 remains affected by the TOCTOU variant. Earlier versions containing the host requirements-reading behavior are affected by the original containment issue; confirm the earliest affected release before setting the advisory’s version range.
Patched version: v1.3.6.
GitHub Advisory Database, CC-BY 4.0. Posts quoted belong to their authors.