# Critical security vulnerabilities reported with go version 1.19.7

**URL:** <https://discuss.elastic.co/t/critical-security-vulnerabilities-reported-with-go-version-1-19-7/330200>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [April 18, 2023, 8:31am UTC](https://discuss.elastic.co/t/critical-security-vulnerabilities-reported-with-go-version-1-19-7/330200 "2023-04-18T08:31:21Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![manojrkrish](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/manojrkrish/32/119948_2.png) [@manojrkrish](https://discuss.elastic.co/u/manojrkrish)\
**Post date:** [April 18, 2023, 8:31am UTC](https://discuss.elastic.co/t/critical-security-vulnerabilities-reported-with-go-version-1-19-7/330200/1 "2023-04-18T08:31:21Z")

</div>

Hi,

Recently few critical vulnerabilities are reported in go version 1.19.7 with below CVEs.

[https://nvd.nist.gov/vuln/detail/CVE-2023-24536](https://nvd.nist.gov/vuln/detail/CVE-2023-24536)  
[https://nvd.nist.gov/vuln/detail/CVE-2023-24537](https://nvd.nist.gov/vuln/detail/CVE-2023-24537)  
[https://nvd.nist.gov/vuln/detail/CVE-2023-24538](https://nvd.nist.gov/vuln/detail/CVE-2023-24538)

Seems these vulnerabilities are addressed with go version 1.19.8. Could someone help in updating go-version used in beats to 1.19.8?

Thanks.

---

<div class="post-metadata">

**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:** [April 18, 2023, 8:39am UTC](https://discuss.elastic.co/t/critical-security-vulnerabilities-reported-with-go-version-1-19-7/330200/2 "2023-04-18T08:39:54Z")

</div>

Welcome to our community! 😃

Please see [Security issues | Elastic](https://www.elastic.co/community/security) for the best way to raise these issues with us, specifically;

> **Other security issues**
> 
> Users and customers may report any other potential security issues to [security@elastic.co](mailto:security@elastic.co). This address can be used for product security related inquiries or requests about other security topics that are not explicitly mentioned here. We can accept only security issues at this address. Bug reports should be directed to the bug database of the project you're reporting it on or raised to Elastic Support.
> 
> If you would like to encrypt your message to us, please use our PGP key. The fingerprint is
> 
> 1224 D1A5 72A7 3755 B61A 377B 14D6 5EE0 D2AE 61D2
> 
> The key is available via keyservers; search for 'security@elastic.co'.

---

<div class="post-metadata">

**Author:** ![manojrkrish](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/manojrkrish/32/119948_2.png) [@manojrkrish](https://discuss.elastic.co/u/manojrkrish)\
**Post date:** [April 20, 2023, 3:58pm UTC](https://discuss.elastic.co/t/critical-security-vulnerabilities-reported-with-go-version-1-19-7/330200/3 "2023-04-20T15:58:41Z")

</div>

Thanks, reported the same to [security@elastic.co](mailto:security@elastic.co).

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 18, 2023, 5:59pm UTC](https://discuss.elastic.co/t/critical-security-vulnerabilities-reported-with-go-version-1-19-7/330200/4 "2023-05-18T17:59:15Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.