router.push with "as" parameter causes infinite loop when using a middleware

Link to the code that reproduces this issue

https://github.com/KmaCoder/reproduce-router-middleware-bug

To Reproduce

1. Add an empty middleware.ts

import { NextMiddleware } from 'next/server';

export const middleware: NextMiddleware = (req) => {
    console.log(`> middleware req.url ${req.url}`)
};

2. Use router.push with an "as" parameter

// On the index page make a redirect to some other page,
// with an 'asPath' = '/' to be shown in browser search bar  
void router.push('/home-redirect', '/')

Current vs. Expected behavior

Current

The page does not change, in network there is an infinite loop of fetching the page JSON /_next/data/.

With middleware.ts:

Expected:

The page changes to the specified one, while the pathname in the browser equals to the as param.

Without middleware.ts, works as expected:

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 22.6.0: Wed Jul  5 22:22:05 PDT 2023; root:xnu-8796.141.3~6/RELEASE_ARM64_T6000
Binaries:
  Node: 18.17.0
  npm: 9.6.7
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.0.4-canary.1
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Middleware / Edge (API routes, runtime), Routing (next/router, next/navigation, next/link)

Additional context

Reproducible since the middleware