CVE-2026-49983
Deno: process.loadEnvFile() bypasses env permission checks and mutates process.env with only read access
Vexday Risk Score
13Low
SSVC decision (CISA)
Track
No exploitation signal → monitor
CVSS 5.2EPSS 0.1%KEV nãoPoC —Nuclei —Metasploit —Patch —
Lifecycle
23 Jun 2026Published on NVD
Recommendation: Monitor — no exploitation signal at the moment.
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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Affected products
denoland · denoWant to know if your infrastructure is exposed to this?
Talk to TrueHacking →