{"version":"2.1.315","anchor":"security-hardening-wildcard-url-check-pem-prefix-check-es","canonical_anchor":"security-hardening-wildcard-url-check-pem-prefix-check-es","heading":"Stricter handling of web address wildcards, certificates and escape codes","tier":"notice","area":"Network Security","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/security-hardening-wildcard-url-check-pem-prefix-check-es","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Stricter handling of web address wildcards, certificates and escape codes\n\nThree internal checks now take the stricter or safer answer: address wildcards, certificate data and stray escape characters\n\n**What**\n\nThree checks inside Claude Code have become stricter:\n\n- Web address wildcards. A wildcard is a character that stands for many possible addresses. Claude Code checks whether an address contains one, and the check first has to decode the address. Before, any error during that decoding counted as \"no wildcard\". Now only a badly encoded address counts that way, and any other error counts as a wildcard being present.\n\n- Certificate data. A check on certificate data now requires the start of the decoded data to match the original bytes exactly.\n\n- Escape characters. A lone escape character is now treated as ordinary text. The escape character is the invisible character that starts terminal control codes.\n\n**Why**\n\nThese are small changes that make each check stricter, or make it take the safer answer when something goes wrong.\n\n- Area: Network Security\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}