github.com/golang-jwt/jwt/v4 - version

[dhamahes]

Bug report criteria

• This bug report is not security related, security issues should be disclosed privately via etcd maintainers.
• This is not a support request or question, support requests or questions should be raised in the etcd discussion forums.
• You have read the etcd bug reporting guidelines.
• Existing open issues along with etcd frequently asked questions have been checked and this is not a duplicate.

What happened?

I have noted that github.com/golang-jwt/jwt/v4 - version 4.5.1 is available in the latest source code.
We are using etcd version 3.5.17 which has 4.4.2 which has now raised vulnerability.
Wanted to know when new version etcd will be release with github.com/golang-jwt/jwt/v4 -4.5.1 version

What did you expect to happen?

I have noted that github.com/golang-jwt/jwt/v4 - version 4.5.1 is available in the latest source code.
We are using etcd version 3.5.17 which has 4.4.2 which has now raised vulnerability.
Wanted to know when new version etcd will be release with github.com/golang-jwt/jwt/v4 -4.5.1 version

How can we reproduce it (as minimally and precisely as possible)?

I have noted that github.com/golang-jwt/jwt/v4 - version 4.5.1 is available in the latest source code.
We are using etcd version 3.5.17 which has 4.4.2 which has now raised vulnerability.
Wanted to know when new version etcd will be release with github.com/golang-jwt/jwt/v4 -4.5.1 version

Anything else we need to know?

No response

Etcd version (please run commands below)

./etcd -version
etcd Version: 3.5.14
Git SHA: bf51a53
Go Version: go1.21.10
Go OS/Arch: linux/amd64

Etcd configuration (command line flags or environment variables)

paste your configuration here

Etcd debug information (please run commands below, feel free to obfuscate the IP address or FQDN in the output)

$ etcdctl member list -w table
# paste output here

$ etcdctl --endpoints=<member list> endpoint status -w table
# paste output here

Relevant log output

[ahrtr]

cc @ivanvc

[ivanvc]

Hi @dhamahes, thanks for reporting this. We'll release this update in 3.5.18. Reference: #18898 / #18901.

I'll close this issue once we do the 3.5.18 release.

Link to #19119