{"version":"2.1.191","anchor":"windows-drive-relative-path-security","canonical_anchor":"windows-drive-relative-path-security","heading":"Windows Drive-Relative Path Security","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.191\/e\/windows-drive-relative-path-security","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.191","markdown":"### Windows Drive-Relative Path Security\n\nWhat changed: Paths of the form `C:filename` (drive-relative, without a backslash) are now flagged and require manual approval rather than being resolved silently.\n\n**Details**\n\n- Drive-relative paths resolve against a per-drive current directory (a Windows quirk), which cannot be statically validated at permission-check time.\n- Approval message: `Path '<path>' is drive-relative (resolves against the per-drive current directory, which cannot be statically validated) and requires manual approval`.\n\n**Evidence**\n\nDrive-relative path check (search for `\"is drive-relative (resolves against the per-drive current directory\"`)"}