The vulnerability stems from improper path handling in the request processing flow. While the exact code isn't available, the advisory indicates the server resolves relative paths without validation. In Node.js static servers, the primary request handler (typically named handleRequest or similar) would be responsible for mapping URL paths to filesystem paths. The high confidence comes from: 1) The vulnerability pattern matches unsafe path.join() operations with user input 2) The attack vector requires no authentication 3) The impact matches unvalidated path resolution behavior 4) This is a fundamental flaw in the core file serving functionality.