Is deno affected by CVE-2021-32619?

crates.io deno is affected in >=1.5.0 <1.10.2.

Is CVE-2021-32619 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 1.1%.

critical

CVE-2021-32619

Q: Is CVE-2021-32619 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 1.1%.

crates.io · deno

Summary

Deno's static imports inside dynamically imported modules do not adhere to permission checks

Severity: critical
EPSS: 1.1% (p62)
Also known as: GHSA-xpwj-7v8q-mcgj
Published: 2021-09-23

References

https://github.com/denoland/deno/security/advisories/GHSA-xpwj-7v8q-mcgj
https://nvd.nist.gov/vuln/detail/CVE-2021-32619
https://github.com/denoland/deno

Related advisories

CVE-2026-22863 — critical · crates.io/deno
CVE-2022-24783 — critical · crates.io/deno
CVE-2026-49440 — high · crates.io/deno
CVE-2026-49402 — high · crates.io/deno
CVE-2026-44726 — high · crates.io/deno
CVE-2026-32260 — high · crates.io/deno
CVE-2026-27190 — high · crates.io/deno
CVE-2026-22864 — high · crates.io/deno

Is your project exposed to this? Stateward checks every dependency on every pull request and flags it only if your code actually reaches it.

Check my repo

Summarize with AI

ChatGPT Claude Perplexity

Sources: CISA KEV (public domain), OSV.dev & GitHub Advisory Database (CC-BY-4.0), FIRST EPSS, NVD/CWE (public domain). Served live from the Stateward advisory database.