deno
Affected
- introduced
0, fixed2.8.1(semver)
Fixed versions
2.8.1
Fix
- Fixed version
2.8.1cargo update -p deno --precise 2.8.1
Advisory
Also known as: CVE-2026-49983
Deno: process.loadEnvFile() bypasses env permission checks and mutates process.env with only read access
Summary
In Deno, environment access is gated by the env permission. You can deny it
with --deny-env, or restrict it to a specific allowlist with--allow-env=FOO,BAR. The expectation is that a program running without env
permission cannot change process.env.
process.loadEnvFile() (the Node-compatible API for loading variables from a.env file) does not honor this. It only checks that the program has
read permission for the dotenv file, then writes every key in that file
into the process environment — even when env access is denied.
In effect, **--allow-read plus a writable or attacker-controlled .env file
is enough to defeat --deny-env.**
Am I affected?
You are potentially affected if all of the following are true:
process.loadEnvFile() from node:process.--deny-env, an --allow-env=… allowlist, or running without granting env — as a security boundary..env path passed to loadEnvFile() can be controlled or modified by a less-trusted party (untrusted input, user-writable directory, third-party dependency, etc.) and is covered by your --allow-read grant.If your program does not use process.loadEnvFile() at all, or if it already
grants full env access, this advisory does not change your risk.
Medium Basis: The source's own band: MODERATE
0, fixed 2.8.1 (semver)2.8.1
2.8.1cargo update -p deno --precise 2.8.1Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0