{"version":"2.1.281","anchor":"permission-wildcard-matcher-rejects-patterns-containing-nul","canonical_anchor":"permission-wildcard-matcher-rejects-patterns-containing-nul","heading":"Permission wildcard matcher rejects patterns containing NUL","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/permission-wildcard-matcher-rejects-patterns-containing-nul","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Permission wildcard matcher rejects patterns containing NUL\n\nPermission rules with wildcards now never match if the pattern contains a NUL byte\n\n**What**\n\nA permission rule pattern that contains a NUL byte now never matches. Permission rules decide what Claude Code may do without asking you. A NUL byte is an invisible zero character. The part that matches `*` wildcards in these rules uses NUL characters internally.\n\n**Why**\n\nA pattern with a NUL in it can no longer mix with those internal markers and match something it should not."}