Repository navigation
Replies: 3 comments
0 replies
|
@wordrak we have been refining as much as we can our security bug triage process to make sure that we fix as much CVEs as we can. Most of the issues are reported here https://github.com/keycloak/keycloak/issues?q=is%3Aissue+sort%3Aupdated-desc+label%3Akind%2Fcve+is%3Aclosed and should be solved in the upcoming release. If there's anything that we are missing, please do not hesitate to create a GH issue. Adding the CVE ID into the title helps a lot. @miguel-carvajal almost all the CVEs you mentioned should be solved with a container re-spin, it should happen in the upcoming release, or before. |
0 replies
|
It should be solved now, at least for the OS dependencies: For Java dependencies, it should be fixed in the upcoming releases. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello,
our Security Team has found some CVEs in the current version of Keycloak. Do you have a plan to fix them?
All reactions