Disclosure summary
In all versions of Node.js 10 prior to 10.9.0, an argument processing flaw can cause `Buffer.alloc()` to return uninitialized memory. This method is intended to be safe and only return initialized, or cleared, memory. The third argument specifying `encoding` can be passed as a number, this is misinterpreted by `Buffer's` internal "fill" method as the `start` to a fill operation. This flaw may be abused where `Buffer.alloc()` arguments are derived from user input to return uncleared memory blocks that may contain sensitive information.
Source-reported weakness categories
CWE-226, CWE-908
Source-specific records & product guidance
Sources retain their own attribution and scoring. Follow the original record to confirm affected versions, fixed releases, and configuration conditions.
NIST NVD · NVD-CVE-2018-7166
Open original source · Updated Oct 08, 2026
Only CPE matches marked vulnerable=true are indexed. AND/OR platform conditions must be checked in the original NVD record.
| Vendor | Product / association | Version / bounds |
|---|---|---|
| nodejs | node.js | * · versionStartIncluding: 10.0.0 · versionEndExcluding: 10.9.0 |
Indexed product associations
These cached associations support search and triage. Confirm applicability, platform conditions, and fixed versions in the original record.
| Vendor | Product | Version | Source / relationship |
|---|---|---|---|
| nodejs | node.js | * | nvd / vulnerable |
Original records & references
- NIST NVD record
- CVE Program record
- cve-request@iojs.org — Third Party Advisory
- cve-request@iojs.org — Vendor Advisory
GitHub repository matches
Repository matches are links and GitHub-supplied metadata only. They are not verified working proof-of-concept code. Each supported query is bounded to ten pages and at most 1,000 indexed results. This is not a complete index of GitHub or public exploit research. Coverage can also be limited by provider availability, rate limits, rejected metadata, incomplete search results, manual review, and the recorded refresh time.
No stored repository matches
Repository discovery has not recorded an update for this CVE yet.
Discovery progress
0 of 3 discovery queries finished. GitHub returned 0 indexed results; 0 malformed or disallowed results were rejected.
No discovery update has been recorded for this CVE.
View all 0 stored repository matches
PUBLISHED 2018-08-21T12:29:00+00:00
MODIFIED 2026-10-08T22:16:48+00:00
INGESTED 2026-10-11T00:50:18+00:00