RepoJournal
Node.js

@nodejs

The Node.js runtime — every backend team's CVE source of truth

Pick a date

  1. Thu 21 may
  2. Sat 23 may
  3. Sun 24 may
  4. Mon 25 may
  5. Tue 26 may
  6. Wed 27 may
  7. Thu 28 may
  8. Fri 29 may
  9. Sat 30 may
  10. Sun 31 may
  11. Mon 1 jun
  12. Mon 8 jun
  13. Tue 9 jun
  14. Wed 10 jun
  15. Thu 11 jun
  16. Fri 12 jun
  17. Sat 13 jun
  18. Sun 14 jun
  19. Mon 15 jun
  20. Tue 16 jun
  21. Wed 17 jun
  22. Thu 18 jun
  23. Fri 19 jun
  24. Sat 27 jun
  25. Sun 28 jun
  26. Mon 29 jun
  27. Tue 30 jun
  28. Wed 1 jul
  29. Thu 2 jul
  30. Today 3 jul

The Wire · Showcase

NODE VFS FIX STOPS SILENT FILE FAILURES ON RENAMED HANDLES

By RepoJournal · Filed · About Node.js

A critical filesystem virtualization bug that caused ENOENT errors when tracked files were renamed after opening is now fixed.

The Virtual FileSystem layer in Node's file handling had a fundamental flaw: when you opened a file and then that file was renamed, subsequent reads through the open file descriptor would fail instead of following the inode like the real filesystem does [1]. The fix moves `RealFileHandle.readFileSync()` and `readFile()` to read through the already-open fd using positioned reads rather than reopening the original path, matching native behavior and preserving handle state [1]. In parallel, the zlib module is tightening its decompression security posture by exposing the previously internal `rejectGarbageAfterEnd` option [2] and applying it to web streams to reject trailing gzip members [3], addressing a class of parsing vulnerabilities. Crypto types are now officially documented [5], and the docs got a scrub to fix broken links and duplicate stability labels [4]. Doc-kit merged a feature to allow titles without markdown syntax [6], improving templating flexibility.

Action items

References

  1. [1] vfs: read RealFSProvider files from open fd ↗ nodejs/node
  2. [2] zlib: expose rejectGarbageAfterEnd option nodejs/node
  3. [3] zlib: reject trailing gzip members in web streams nodejs/node
  4. [4] doc: fix broken links and duplicate stability label nodejs/node
  5. [5] typings: add typing for crypto nodejs/node
  6. [6] feat(title): allow no-md title ↗ nodejs/doc-kit

FAQ

What changed in Node.js on June 28, 2026?
A critical filesystem virtualization bug that caused ENOENT errors when tracked files were renamed after opening is now fixed.
What should Node.js teams do about it?
Test VFS-backed file operations if you use virtual filesystems or file tracking • Review zlib decompression streams for exposure to concatenated gzip members • Update to latest Node when released to get the VFS handle fix
Which Node.js repositories shipped on June 28, 2026?
nodejs/node, nodejs/doc-kit

Related across the cluster

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.