# ELK Security

**URL:** <https://discuss.elastic.co/t/elk-security/363722>\
**Category:** Kibana\
**Created:** [July 24, 2024, 2:35pm UTC](https://discuss.elastic.co/t/elk-security/363722 "2024-07-24T14:35:53Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ankita\_Pachauri](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ankita_pachauri/32/61469_2.png) [@Ankita\_Pachauri](https://discuss.elastic.co/u/Ankita_Pachauri)\
**Post date:** [July 24, 2024, 2:35pm UTC](https://discuss.elastic.co/t/elk-security/363722/1 "2024-07-24T14:35:53Z")

</div>

Hi Team,

We just upgraded the stack version on 8.14.0 and the vulnerability scan has picked up CVE-2024-27980, CVE-2024-22020, CVE-2024-36137, CVE-2024-22018 and CVE-2024-37372. Can you please let me know how it impacts the Kibana instance and is there is a fix for this?

---

<div class="post-metadata">

**Author:** ![vitaliidm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vitaliidm/32/101610_2.png) [@vitaliidm](https://discuss.elastic.co/u/vitaliidm)\
**Post date:** [July 24, 2024, 2:49pm UTC](https://discuss.elastic.co/t/elk-security/363722/2 "2024-07-24T14:49:37Z")

</div>

From #Elastic Security to #Kibana

---

<div class="post-metadata">

**Author:** ![Ankita\_Pachauri](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ankita_pachauri/32/61469_2.png) [@Ankita\_Pachauri](https://discuss.elastic.co/u/Ankita_Pachauri)\
**Post date:** [July 29, 2024, 2:33pm UTC](https://discuss.elastic.co/t/elk-security/363722/3 "2024-07-29T14:33:40Z")

</div>

Hi,  
Can I get some update on this?

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [July 29, 2024, 2:54pm UTC](https://discuss.elastic.co/t/elk-security/363722/4 "2024-07-29T14:54:52Z")

</div>

You need to send an email to `security@elastic.co` with those CVE so the security team can check if they impact any tool in the stack or not.

If you do not send the email Elastic will not validate this.

---

<div class="post-metadata">

**Author:** ![Ankita\_Pachauri](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ankita_pachauri/32/61469_2.png) [@Ankita\_Pachauri](https://discuss.elastic.co/u/Ankita_Pachauri)\
**Post date:** [July 29, 2024, 2:55pm UTC](https://discuss.elastic.co/t/elk-security/363722/5 "2024-07-29T14:55:59Z")

</div>

Hi,  
I have already sent an email for this, however did not get any response. Hence, I opened this case on the forum.

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [July 29, 2024, 3:07pm UTC](https://discuss.elastic.co/t/elk-security/363722/6 "2024-07-29T15:07:42Z")

</div>

I don't think they check this forum often, it is not considered official support.

If you have a support contract, opening a ticket may speed up things, but besides that I don't think there is much else to do.

---

<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:** [August 26, 2024, 3:08pm UTC](https://discuss.elastic.co/t/elk-security/363722/7 "2024-08-26T15:08:13Z")

</div>

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