# Upgraded go version for 2.7.x **URL:** \ **Category:** Elastic Cloud on Kubernetes (ECK)\ **Created:** [May 16, 2023, 9:18pm UTC](https://discuss.elastic.co/t/upgraded-go-version-for-2-7-x/333608 "2023-05-16T21:18:52Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![zpear](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zpear/32/88772_2.png) [@zpear](https://discuss.elastic.co/u/zpear)\ **Post date:** [May 16, 2023, 9:18pm UTC](https://discuss.elastic.co/t/upgraded-go-version-for-2-7-x/333608/1 "2023-05-16T21:18:52Z")
Hi all, I'm currently running ECK 2.7.0 but noticed a critical injection cve, CVE-2023-24538, that's brought in from the version of golang ECK runs with. I see since then, the go version has been updated ([Update docker.io/library/golang Docker tag to v1.20.4 by renovate[bot] · Pull Request #6752 · elastic/cloud-on-k8s · GitHub](https://github.com/elastic/cloud-on-k8s/pull/6752)). Would it be possible to release 2.7.x with the upgraded go version to avoid this vulnerability? Alternatively, when is 2.8.0 scheduled to be released? Thanks ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [May 16, 2023, 11:58pm UTC](https://discuss.elastic.co/t/upgraded-go-version-for-2-7-x/333608/2 "2023-05-16T23:58:39Z")
Please see [Security issues | Elastic](https://www.elastic.co/community/security) for the best way to get a response for possible security issues like this 🙂 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 13, 2023, 11:58pm UTC](https://discuss.elastic.co/t/upgraded-go-version-for-2-7-x/333608/3 "2023-06-13T23:58:46Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.