{"version":"2.1.261","anchor":"chrome-extension-file-upload-path-validation-hardened-and-re","canonical_anchor":"chrome-extension-file-upload-path-validation-hardened-and-re","heading":"Chrome extension file_upload path validation hardened and reused","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261\/e\/chrome-extension-file-upload-path-validation-hardened-and-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261","markdown":"### Chrome extension file_upload path validation hardened and reused\n\nFile-upload path safety checks were refactored into shared helpers reused across upload paths.\n\nThe `file_upload` tool's path-safety checks, covering network path rejection, Windows-path spoofing detection, percent-encoding\/`..` rejection, and kernel alias-namespace rejection (paths like `\/dev`, `\/proc`, `..namedfork`), are now factored into shared helper functions. These are applied both to a new lightweight pass-through validation path and the existing full resolve-and-check path, tightening protection against path traversal and spoofing when Claude-in-Chrome uploads local files.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}