# Impact of CVE-2025-68161 on Elasticsearch **URL:** \ **Category:** Elastic Security\ **Created:** [January 30, 2026, 10:00am UTC](https://discuss.elastic.co/t/impact-of-cve-2025-68161-on-elasticsearch/384828 "2026-01-30T10:00:49Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![georgii](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/georgii/32/78076_2.png) [@georgii](https://discuss.elastic.co/u/georgii)\ **Post date:** [January 30, 2026, 10:25am UTC](https://discuss.elastic.co/t/impact-of-cve-2025-68161-on-elasticsearch/384828/2 "2026-01-30T10:25:13Z")
Hi @amolrm, According to the [official statement](https://support.elastic.co/knowledge/security-ESST-c3551093-6357-49d3-b6b4-3648496ea77d) of Elastic, Elasticsearch is **not affected** by CVE-2025-68161. Please find other CVE-related statements on the Support portal: [support.elastic.co/search/?search.category=cve](https://support.elastic.co/search/?search.category=cve). To report a security vulnerability, please send an email to [security@elastic.co](mailto:security@elastic.co) with details of the vulnerability. Hope this is useful. Thank you! --- _[View the full topic](https://discuss.elastic.co/t/impact-of-cve-2025-68161-on-elasticsearch/384828)._