# Elasticsearch Vulnerability Patches **URL:** \ **Category:** Elasticsearch\ **Created:** [July 5, 2018, 1:21pm UTC](https://discuss.elastic.co/t/elasticsearch-vulnerability-patches/138723 "2018-07-05T13:21:30Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![vikas\_gopal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vikas_gopal/32/47661_2.png) [@vikas\_gopal](https://discuss.elastic.co/u/vikas_gopal)\ **Post date:** [July 5, 2018, 1:21pm UTC](https://discuss.elastic.co/t/elasticsearch-vulnerability-patches/138723/1 "2018-07-05T13:21:30Z")
Hi Experts , I was checking below document [https://www.elastic.co/community/security](https://www.elastic.co/community/security) Here I saw Vulnerability Summary along with the Remediation. Generally it asks to upgrade to 6.X or to the latest release . My concern here is what if I am not in position to upgrade my entire stack can this CVE be separately installed as a patch ? Just for an example CVE-2018-3827 is really important in my case but as a remediation I need to upgrade to 6.3 . Is there any other alternate ? Regrads Vikas ---
**Author:** ![ikakavas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ikakavas/32/34430_2.png) [@ikakavas](https://discuss.elastic.co/u/ikakavas)\ **Post date:** [July 13, 2018, 1:17pm UTC](https://discuss.elastic.co/t/elasticsearch-vulnerability-patches/138723/2 "2018-07-13T13:17:33Z")
Hello @vikas_gopal, Thank you for raising this. The aforementioned issue is also fixed in 5.6.10, we will make sure to update our notes. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 10, 2018, 1:17pm UTC](https://discuss.elastic.co/t/elasticsearch-vulnerability-patches/138723/3 "2018-08-10T13:17:34Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.