Runner 17.5 breaks cross project submodule authentication with job token

Summary

Runner 17.5 seems to break cross project submodule authentication with job tokens.

When reverting back to runner 17.4.1 it works.

Cloning into '/builds/example/example/git/example/example_data/example_data'...
fatal: could not read Username for 'https://example.com': No such device or address
fatal: clone of 'https://example.com/example/example_data/example_data.git' into submodule path '/builds/example/example/git/example/example_data/example_data' failed
Failed to clone 'example_data/example_data'. Retry scheduled

Steps to reproduce

Have a submodule in a project from the same gitlab domain. Allow job tokes access. -> Submodule cannot be updated on the gitlab runner 17.5

.gitlab-ci.yml

Add the job definition that is failing here

Actual behavior

Runner 17.5 cannot authenticate with job tokens to update a submodule from the same domain.

Expected behavior

Runner 17.5 can authenticate with a job token to update a submodule from the same domain.

Relevant logs and/or screenshots

job log

Add the job log

Environment description

We install gitlab runner from debian packages on Ubuntu 20.04

config.toml contents

Add your configuration here

Used GitLab Runner version

Possible fixes

Revert back to gitlab runner 17.4.1.