# Impact of CVE-2025-68161 on Elasticsearch v7.17.28

**URL:** <https://discuss.elastic.co/t/impact-of-cve-2025-68161-on-elasticsearch-v7-17-28/384825>\
**Category:** Elasticsearch\
**Created:** [January 30, 2026, 9:51am UTC](https://discuss.elastic.co/t/impact-of-cve-2025-68161-on-elasticsearch-v7-17-28/384825 "2026-01-30T09:51:16Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![carly.richmond](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carly.richmond/32/104935_2.png) [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)\
**Post date:** [January 30, 2026, 3:41pm UTC](https://discuss.elastic.co/t/impact-of-cve-2025-68161-on-elasticsearch-v7-17-28/384825/3 "2026-01-30T15:41:48Z")

</div>

@amolrm try to avoid cross-posting the same question in multiple topics. But as confirmed [here](https://discuss.elastic.co/t/impact-of-cve-2025-68161-on-elasticsearch/384828/2) Elastic and Elasticsearch are not impacted.

Hope that helps!

---

_[View the full topic](https://discuss.elastic.co/t/impact-of-cve-2025-68161-on-elasticsearch-v7-17-28/384825)._