-
Notifications
You must be signed in to change notification settings - Fork 9.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Address CVE-2023-3635 #8050
Labels
bug
Bug in existing code
Comments
Yep, that's the plan. But it isn't blocking you, you can specify a higher okio version in your build to fix the issue. If it continues to warn it's broken audits. But release will happen, just when ready. |
Closing as a dupe |
Does anyone have a guess when a new 4.x release might be released? |
I’d like to do a release in the next 7 days. |
4.12.0 released |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current version of Okhttp (
4.11.0
) ships with a vulnerable version of Okio (CVE-2023-3635). I noticed that the current master branch already has a newer version that is not vulnerable.Please publish a new Okhttp version so the library doesn't ship with a vulnerable dependency anymore.
The text was updated successfully, but these errors were encountered: