Details
{
"platform": "win32",
"slashTraversalStatus": 404,
"slashTraversalRejected": true,
"backslashTraversalStatus": 200,
"backslashTraversalReturnedOutsideCanary": true,
"returnedBody": "SYNTHETIC_OUTSIDE_ROOT_CANARY",
"expectedBackslashTraversalBlocked": false
}
The same result was observed with @vitest/[email protected].
This includes two useful controls:
traversal:../secret.txtis rejected and returns 404, confirming the published forward-slash fix is active.traversal:..\secret.txtreturns 200 and the exact outside-root canary, confirming a Windows separator bypass rather than an unrelated route or fixture response.