Skip to content

CVE-2026-49983 Deno: process.loadEnvFile() bypasses env permission checks and mutates process.env with only read access

MediumCVSS 5.2 EPSS 0.14%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
No known exploitation · automatable: no · technical impact: partial

Description

Deno is a JavaScript, TypeScript, and WebAssembly runtime. Prior to 2.8.1, 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. This vulnerability is fixed in 2.8.1.

Upgrade path

3 packages: 2 fixed.

PackageAffectedFixed inStatus
crates.io deno(crates.io) < 2.8.1; <= 2.8.0 2.8.1 Fixed
deno >= 2.3.0, < 2.8.1 2.8.1 Fixed
denoland deno = < 2.8.1 No fix listed Versions listed

Affected products

ProductAffected versionsFixed in
crates.io deno(crates.io) < 2.8.1 2.8.1
denoland deno = < 2.8.1 No fix listed
crates.io deno(crates.io) <= 2.8.0 No fix listed
deno >= 2.3.0, < 2.8.1 2.8.1

References