[Bug]: Critical security vulnerability introduced by jersey-client 3.0.10

Description

Critical security vulnerability introduced by jersey-client 3.0.10: https://security.snyk.io/package/maven/org.glassfish.jersey.core%3Ajersey-client/3.0.10

Swagger Codegen Version

3.0.75

Language / Generator

Java

OpenAPI/Swagger Spec

Command Line Used

mvn dependency:tree -Dverbose -DoutputFile=dependency-tree.txt

Steps to Reproduce

Snyk scan on the repository

Expected Behavior

No more critical issue by upgrading this dependency to v3.0.17: https://security.snyk.io/package/maven/org.glassfish.jersey.core%3Ajersey-client/3.0.17

Actual Behavior

jersey-client critical vulnerability

Related Issues / Repos

Environment

• OS:
• Java Version:
• Build Tool:
• Swagger Codegen CLI version:

Additional Context

Checklist

• I have searched the existing issues to make sure this is not a duplicate.
• I have included a minimal and reproducible spec example.
• I have explained how to reproduce the issue.
• I have specified which generator/language is affected.

Start by running the reported Maven dependency tree command and inspect dependency-tree.txt to identify where jersey-client 3.0.10 is introduced. Update that dependency to 3.0.17, then rerun the dependency check or Snyk scan and confirm the critical vulnerability is gone.