CVE-2026-49983

MEDIUMPre-NVD 5.25.2—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 99% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.2
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.2Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
5.2
EG Score
5.2(medium)
EPSS
1.0%
KEV
Not listed

Published

June 16, 2026

Last Modified

June 29, 2026

Advisory Details (1)

Auto-updated Jun 23, 2026
Patch available. Sources: github.
github Patch Available

process.loadEnvFile() bypasses env permission checks and mutates process.env with only read access · Advisory · denoland/deno · GitHub

https://github.com/denoland/deno/security/advisories/GHSA-4c8g-jvcx-v4hv

Vendor Advisories for CVE-2026-49983(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
crates.io(1)
PackageVulnerable rangeFixed inDependents
deno—2.8.1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 33× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 23:08 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-05 09:39 UTCEG score recompute
  4. 2026-07-05 02:30 UTCEPSS rescore
  5. 2026-07-04 09:08 UTCEG score recompute
  6. 2026-07-04 06:31 UTCEPSS rescore
  7. 2026-07-03 04:09 UTCEG score recompute
  8. 2026-07-02 03:34 UTCEG score recompute
  9. 2026-07-01 15:07 UTCEPSS rescore
  10. 2026-07-01 03:03 UTCEG score recompute
  11. 2026-06-30 23:22 UTCEPSS rescore
  12. 2026-06-30 02:32 UTCEG score recompute
  13. 2026-06-29 14:06 UTCEPSS rescore
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-29 02:01 UTCEG score recompute
  16. 2026-06-28 14:07 UTCEPSS rescore
  17. 2026-06-28 04:56 UTCEPSS rescore
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-28 01:30 UTCEG score recompute
  20. 2026-06-27 03:08 UTCEPSS rescore
  21. 2026-06-27 00:59 UTCEG score recompute
  22. 2026-06-26 00:27 UTCEG score recompute
  23. 2026-06-25 13:49 UTCEPSS rescore
  24. 2026-06-24 23:40 UTCEG score recompute
  25. 2026-06-24 14:05 UTCEPSS rescore
Show 8 more
  1. 2026-06-23 23:09 UTCEG score recompute
  2. 2026-06-22 22:38 UTCEG score recompute
  3. 2026-06-21 22:03 UTCEG score recompute
  4. 2026-06-20 21:26 UTCEG score recompute
  5. 2026-06-19 20:54 UTCEG score recompute
  6. 2026-06-18 20:14 UTCEG score recompute
  7. 2026-06-17 19:37 UTCEG score recompute
  8. 2026-06-16 19:06 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-49983?
CVE-2026-49983 is a medium vulnerability published on June 16, 2026. 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…
When was CVE-2026-49983 disclosed?
CVE-2026-49983 was first published in the National Vulnerability Database on June 16, 2026, with the most recent update on June 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49983 actively exploited?
CVE-2026-49983 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-49983?
CVE-2026-49983 has a CVSS v3 base score of 5.2 (NVD).
How do I remediate CVE-2026-49983?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49983, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49983

Explore →

Is Your Infrastructure Affected by CVE-2026-49983?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs