CVE-2017-16026

UNKNOWNCVSS 0.0

0.0

Request is an http client. If a request is made using ``multipart`, and the body type is a `number``, then the specified number of non-zero memory is passed in the body. This affects Request >=2.2.6 <2.47.0 || >2.51.0 <=2.67.0.

CVSS v3: —
EG Score: —
EPSS: —
KEV: Not listed

Published

June 4, 2018

Last Modified

November 21, 2024

References (6)

support@hackeronehttps://github.com/request/request/issues/1904
support@hackeronehttps://github.com/request/request/pull/2018
support@hackeronehttps://nodesecurity.io/advisories/309
af854a3a-2127-422b-91ae-364da2661108https://github.com/request/request/issues/1904
af854a3a-2127-422b-91ae-364da2661108https://github.com/request/request/pull/2018
af854a3a-2127-422b-91ae-364da2661108https://nodesecurity.io/advisories/309

Affected Packages

(1 across 1 ecosystem)

npm(1)

Package	Vulnerable range	Fixed in	Dependents
request	—	2.68.0	—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 7× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-05-27 16:05 UTCOSV refresh
2026-05-27 13:38 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch

Frequently asked(3)

What is CVE-2017-16026?

CVE-2017-16026 is a unknown vulnerability published on June 4, 2018. Request is an http client. If a request is made using , and the body type is a , then the specified number of non-zero memory is passed in the body. This affects Request >=2.2.6 <2.47.0 || >2.51.0 <=2.67.0.

When was CVE-2017-16026 disclosed?

CVE-2017-16026 was first published in the National Vulnerability Database on June 4, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

How do I remediate CVE-2017-16026?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-16026, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-16026

Explore →

Is Your Infrastructure Affected by CVE-2017-16026?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs