Rust advisories / crate
Security history · deno_runtime · data from Oct 24, 2026
Is deno_runtime safe to use? Its security history
VerdictNo open advisories. 6 past vulnerabilities were fixed.
6advisories on record
6vulnerabilities
0unmaintained notices
nonenewest fixed version
Every advisory, newest first
- VulnerabilityGHSA-7w8p-chxq-2789 · 2025-06-04Deno.env.toObject() ignores the variables listed in --deny-env and returns all environment variables
- VulnerabilityGHSA-xqxc-x6p3-w683 · 2025-06-04Deno run with --allow-read and --deny-read flags results in allowed
- VulnerabilityGHSA-m4pq-fv2w-6hrw · 2024-03-05Deno's deno_runtime vulnerable to interactive permission prompt spoofing via improper ANSI stripping
- VulnerabilityGHSA-vc52-gwm3-8v2f · 2023-05-31Missing "--allow-net" permission check for built-in Node modules
- VulnerabilityGHSA-vq67-rp93-65qf · 2023-03-24Interactive `run` permission prompt spoofing via improper ANSI neutralization
- VulnerabilityGHSA-c25x-cm9x-qqgx · 2023-03-23Deno improperly handles resizable ArrayBuffer
Check your version
Run cargo tree -i deno_runtime to see which version you build and why, or paste your Cargo.lock into the Cargo.toml checker to match every advisory against your exact versions.
RustSec advisories (CC0-1.0) and GitHub-reviewed advisories via OSV's crates.io export, downloaded Oct 24, 2026.
Up next
Are you affected?Check your whole dependency treeRead it next →Also worth your time
Did this answer your question?