Missing "--allow-net" permission check for built-in Node modules

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.6 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N

EPSS

• CVE-2023-33966: 0.63% estimated exploitation activity in the next 30 days; percentile 50.04 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Outbound HTTP requests made using the built-in "node:http" or "node:https" modules are incorrectly not checked against the network permission allow list (--allow-net). Dependencies relying on these built-in modules are subject to the vulnerability too. Users of Deno versions prior to 1.34.0 are unaffected. Deno Deploy users are unaffected. Patches This problem has been patched in Deno v1.34.1 and all users are recommended to update to this version. Workarounds No workaround is available for this issue.

Published by the source

31 May 2023, 23:39 UTC

Last modified by the source

4 Nov 2023, 05:03 UTC

Source last checked

26 Oct 2026, 15:37 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-vc52-gwm3-8v2f

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-33966

Advisory: Missing "--allow-net" permission check for built-in Node modules
IDs: CVE-2023-33966, GHSA-vc52-gwm3-8v2f
Record: https://patchnext.com/advisories/cve-2023-33966 (revision 1, source checked 26 Oct 2026, 15:37 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: deno_runtime 0.115.0; deno 1.34.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io deno_runtime: affected >= 0.114.0, <= 0.114.0; fixed in 0.115.0
- crates.io deno: affected >= 1.34.0, <= 1.34.0; fixed in 1.34.1

## Suggested inspection (read-only)
- crates.io deno_runtime: check the installed version with your package manager.
- crates.io deno: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on deno_runtime, deno.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-vc52-gwm3-8v2f (GitHub-reviewed advisory GHSA-vc52-gwm3-8v2f lists affected ranges: crates.io deno >=1.34.0 =0.114.0 <=0.114.0)

Commands are suggestions: review each one before running it.