How severe is CVE-2025-48888?

No CVSS score has been assigned to CVE-2025-48888 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-48888?

CVE-2025-48888 affects the following packages: deno (crates.io), deno (crates.io), deno (crates.io), deno_runtime (crates.io). Ecosystems affected: crates.io.

How do I fix CVE-2025-48888?

Update deno to 2.1.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-48888 is resolved across your whole dependency graph.

How do I detect CVE-2025-48888 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for deno, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-48888 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2025-48888 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-48888 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-48888?

CVE-2025-48888 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 37th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-48888?

CVE-2025-48888 is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-48888 published, and has it been updated?

CVE-2025-48888 was published on June 4, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

CVE-2025-48888 — deno

Fix: denoland/deno@2f0fae9

CVE-2025-48888 is a CWE-863 vulnerability in deno. A fix is available for deno — see the affected versions and patch details below.

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

Also known asGHSA-xqxc-x6p3-w683

Published

Jun 4, 2025

Updated

Oct 28, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-48888.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs37th percentile — riskier than 37% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

4 pkgs affected

🦀deno🦀deno🦀deno🦀deno_runtime

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

Deno is a JavaScript, TypeScript, and WebAssembly runtime. Starting in version 1.41.3 and prior to versions 2.1.13, 2.2.13, and 2.3.2, deno run --allow-read --deny-read main.ts results in allowed, even though 'deny' should be stronger. The result is the same with all global unary permissions given as --allow-* --deny-*. This only affects a nonsensical combination of flags, so there shouldn't be a real impact on the userbase. Users may upgrade to version 2.1.13, 2.2.13, or 2.3.2 to receive a patch.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`deno`	≥ 1.41.3&&< 2.1.13	2.1.13`cargo update -p deno --precise 2.1.13`
🦀crates.io	`deno`	≥ 2.2.0&&< 2.2.13	2.2.13`cargo update -p deno --precise 2.2.13`
🦀crates.io	`deno`	≥ 2.3.0&&< 2.3.2	2.3.2`cargo update -p deno --precise 2.3.2`
🦀crates.io	`deno_runtime`	≥ 0.150.0&&< 0.212.0	0.212.0`cargo update -p deno_runtime --precise 0.212.0`

Affected Products

1 product · 3 configurations

Application

denodeno

≥ 2.3.0 && < 2.3.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for deno, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update deno to 2.1.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-48888 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

Deno is a JavaScript, TypeScript, and WebAssembly runtime. Starting in version 1.41.3 and prior to versions 2.1.13, 2.2.13, and 2.3.2, `deno run --allow-read --deny-read main.ts` results in allowed, even though 'deny' should be stronger. The result is the same with all global unary permissions given as `--allow-* --deny-*`. This only affects a nonsensical combination of flags, so there shouldn't be a real impact on the userbase. Users may upgrade to version 2.1.13, 2.2.13, or 2.3.2 to receive a patch.

O3 Security · Impact-Aware SCA

Is CVE-2025-48888 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works