Replies: 4 comments 1 reply
|
Would it make sense to track the V8 security fixes separately from the Node.js dependency update? I'm wondering whether all the fixes from V8 14.7 and 14.8 can be backported individually, or whether updating the bundled V8 version is necessary to avoid missing fixes or introducing inconsistencies. It might also be worth checking whether the proposed update changes any Node.js-specific patches or ABI compatibility assumptions. |
|
Thanks for raising this. I checked the official Node.js release information, and there are a few important details worth considering. 1. The V8 version is still 14.6 Node.js 26.13.0, released on October 28, 2026, still reports V8 The release announcement also confirms that 26.13.0 contains no additional code changes compared with 26.12.1. 2. Node.js already uses selective V8 backports The Node.js 26.12.1 security release includes a V8 backport ( This demonstrates that V8 fixes can be incorporated without necessarily upgrading the entire V8 dependency. However, this does not establish whether any of the nine CVEs listed here have already been addressed. 3. Backporting versus upgrading V8 Both approaches have trade-offs:
4. Vulnerability scanner results A scanner matching only the reported V8 version may continue flagging vulnerabilities even when individual fixes have been backported. For accurate tracking, it would be helpful to map each CVE to its corresponding upstream fix and determine whether that patch exists in the Node.js V8 fork. Question for the Node.js maintainers: Is there an existing tracking issue or security advisory covering these nine CVEs for Node.js 26? Specifically, are the fixes being evaluated for individual backporting, or is a V8 version upgrade being considered? Having an official mapping between the CVEs and the actual patch status would help users distinguish confirmed vulnerabilities from version-based scanner findings. References: |
|
Thanks for the detailed report. Node.js generally does not bump V8 to a new major.minor version within a release line (here 14.6 to 14.7 or 14.8). That is done to keep the embedder API and ABI stable for native addons. Instead, V8 security fixes are cherry-picked (backported) into the V8 version the line already ships. This means:
Also, several V8 CVEs only affect specific configurations, such as the Turbofan JIT paths. Their real impact depends on whether untrusted JavaScript is executed, so they matter most when running untrusted code. For the latest status, check the Node.js security releases page (https://nodejs.org/en/blog/vulnerability) and the 26.x changelog. |
|
Thanks for compiling these, Has anyone checked which of the nine CVEs affect Node.js 26.12.1 and whether any fixes have already been backported? If there’s a public issue or advisory tracking this, a link would help others seeing the same scanner results decide whether they need to upgrade. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Node.js 26.12.1 ships V8 14.6.202.34. Vulnerability scanners match on the V8 version and report 9 published V8 CVEs as open for it. All 9 are fixed in V8 14.7 or 14.8, and V8 14.8.178.28 contains all of them.
Are there plan to address these CVEs in Node.js 26 ?
CVEs fixed in V8 14.7:
CVEs fixed in V8 14.8 (14.8.178.28):
Most of these are type confusions, out-of-bounds reads or writes, and integer overflows in V8 and Turbofan.
All reactions