Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

GHSA-7xfp-9c55-5vqj

MEDIUM

GHSA-7xfp-9c55-5vqj is a medium-severity (CVSS 5.9) CWE-201 vulnerability in request. 3 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-7xfp-9c55-5vqj is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Remote Memory Exposure in request

Also known asCVE-2017-16026
Published
Nov 9, 2018
Updated
Nov 8, 2023
Affected
2 pkgs
Patched
2 / 2
Exploits
3 known

Blast Radius

2 pkgs affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

requestnpm
14.5Mdownloads / week

Description

Affected versions of request will disclose local system memory to remote systems in certain circumstances. When a multipart request is made, and the type of body is number, then a buffer of that size will be allocated and sent to the remote server as the body.

Proof of Concept

var request = require('request');
var http = require('http');

var serveFunction = function (req, res){
	req.on('data', function (data) {
            console.log(data)
        });
	res.end();
};
var server = http.createServer(serveFunction);
server.listen(8000);

request({
	method: "POST",
	uri: 'http://localhost:8000',
	multipart: [{body:500}]
},function(err,res,body){});

Recommendation

Update to version 2.68.0 or later

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
📦npmrequest2.49.0&&< 2.68.02.68.0
📦npmrequest2.2.6&&< 2.68.02.68.0
Exploits & PoCs
3

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for request. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update request to 2.68.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7xfp-9c55-5vqj is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-7xfp-9c55-5vqj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-7xfp-9c55-5vqj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Affected versions of `request` will disclose local system memory to remote systems in certain circumstances. When a multipart request is made, and the type of `body` is `number`, then a buffer of that size will be allocated and sent to the remote server as the body. ## Proof of Concept ```js var request = require('request'); var http = require('http'); var serveFunction = function (req, res){ req.on('data', function (data) { console.log(data) }); res.end(); }; var server = http.createServer(serveFunction); server.listen(8000); request({ method: "POST", uri: 'http://
O3 Security · Impact-Aware SCA

Is GHSA-7xfp-9c55-5vqj in your dependencies?

O3 detects GHSA-7xfp-9c55-5vqj across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.