Go related CVEs raised during Twistlock scanning resolution timeline by upgrading go version

[guyibm]

Preflight checklist

• [X] I could not find a solution in the existing issues, docs, nor discussions.
• [X] I agree to follow this project's Code of Conduct.
• [X] I have read and am following this repository's Contribution Guidelines.
• [ ] This issue affects my Ory Network project.
• [ ] I have joined the Ory Community Slack.
• [ ] I am signed up to the Ory Security Patch Newsletter.

Describe the bug

Will the Go version of the project be updated to latest 1.19.x to address CVEs such as https://nvd.nist.gov/vuln/detail/CVE-2022-41715. I see Go on version 1.19.1 in the latest Hydra version v2.0.3. CVEs like this one are being raised during Twistlock scanning for the Go version. Would this be in the next release (v2.0.4) and would you happen to know the timeline for that release?

Reproducing the bug

Run Twistlock scan on Hydra image.

Relevant log output

No response

Relevant configuration

No response

Version

v2.0.3

On which operating system are you observing this issue?

None

In which environment are you deploying?

Kubernetes

Additional Context

No response

[aeneasr]

Thank you for the report. The listed CVEs do not affect Ory Hydra's code base. In the future, please follow our security policy: https://github.com/ory/hydra/security/policy