CVE-2025-48888: Deno run with --allow-read and --deny-read flags results in allowed

CVE-2025-48888 · Severity: low · CVSS 3.1 · Published 2025-06-04

Deno run with --allow-read and --deny-read flags results in allowed

Technologies: deno (crates.io), deno_runtime (crates.io). Vendors: crates.io.

Quick answers

Is CVE-2025-48888 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-48888 being exploited in the wild.
How severe is CVE-2025-48888?
Low severity, with a CVSS score of 3.1, published 4 June 2025.
Which products and versions are affected?
deno (crates.io) SEMVER:introduced=1.41.3,fixed=2.1.13; deno_runtime (crates.io) SEMVER:introduced=0.150.0,fixed=0.212.0.
Is there a fix for CVE-2025-48888?
Yes. deno (crates.io): upgrade to 2.1.13 or later; deno_runtime (crates.io): upgrade to 0.212.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-48888?
Check whether you run deno (crates.io) or deno_runtime (crates.io) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • deno (crates.io): upgrade to 2.1.13 or later
    cargo update -p deno
  • deno_runtime (crates.io): upgrade to 0.212.0 or later
    cargo update -p deno_runtime

Affected products

  • deno (crates.io) SEMVER:introduced=1.41.3,fixed=2.1.13
  • deno_runtime (crates.io) SEMVER:introduced=0.150.0,fixed=0.212.0

Identifiers

  • CVE-2025-48888
  • GHSA-xqxc-x6p3-w683

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.