Remote Memory Disclosure in bittorrent-dht

Exploitation

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

CVSS

not scored

EPSS

• CVE-2016-10519: 1.61% estimated exploitation activity in the next 30 days; percentile 75.99 (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.

Versions of bittorrent-dht prior to 5.1.3 are affected by a remote memory disclosure vulnerability. This vulnerability allows an attacker to send a specific series of of messages to a listening peer and get it to reveal internal memory. There are two mitigating factors here, that slightly reduce the impact of this vulnerability: 1. Any modern kernel will zero out new memory pages before handing them off to a process. This means that only memory previously used and deallocated by the node process can be leaked. 1. Node.js manages Buffers by creating a few large internal SlowBuffers, and slicing them up into smaller Buffers which are made accessible in JS. They are not stored on V8's heap, because garbage collection would interfere. The result is that only memory that has been previously allocated as a Buffer can be leaked. Recommendation Update to version 5.1.3 or later.

Published by the source

1 Sep 2020, 15:22 UTC

Last modified by the source

8 Nov 2023, 03:58 UTC

Source last checked

26 Oct 2026, 12:09 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-77g4-36jp-5v3m

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-77g4-36jp-5v3m

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

# Patch Next advisory brief: CVE-2016-10519

Advisory: Remote Memory Disclosure in bittorrent-dht
IDs: CVE-2016-10519, GHSA-77g4-36jp-5v3m
Record: https://patchnext.com/advisories/cve-2016-10519 (revision 2, source checked 26 Oct 2026, 12:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: bittorrent-dht 5.1.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm bittorrent-dht: affected < 5.1.3; fixed in 5.1.3

## Suggested inspection (read-only)
- `npm ls bittorrent-dht --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## 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 bittorrent-dht.
- 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://osv.dev/vulnerability/GHSA-77g4-36jp-5v3m (OSV record GHSA-77g4-36jp-5v3m lists affected ranges: npm bittorrent-dht >=0 <5.1.3 (fixed))
- Verified: https://github.com/advisories/GHSA-77g4-36jp-5v3m (GitHub-reviewed advisory GHSA-77g4-36jp-5v3m lists affected ranges: npm bittorrent-dht >=0 <5.1.3)

Commands are suggestions: review each one before running it.