{"version":"2.1.281","anchor":"paths-containing-a-nul-byte-are-rejected-before-opening","canonical_anchor":"paths-containing-a-nul-byte-are-rejected-before-opening","heading":"Paths containing a NUL byte are rejected before opening","tier":"internal","area":"File Access","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/paths-containing-a-nul-byte-are-rejected-before-opening","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Paths containing a NUL byte are rejected before opening\n\nFile paths that contain a NUL byte are now rejected before Claude Code tries to open them\n\n**What**\n\nA NUL byte is an invisible zero character that is not valid in file names. A helper that opens files now refuses any path containing one and returns nothing instead of trying to open it.\n\n**Why**\n\nMalformed paths are stopped early rather than reaching the file system.\n\n- Area: File Access\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}