# Impact of CVE-2025-68161 on Elasticsearch v7.17.28 **URL:** \ **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:** 5\ **Page:** 1
**Author:** ![amolrm](https://avatars.discourse-cdn.com/v4/letter/a/e495f1/32.png) [@amolrm](https://discuss.elastic.co/u/amolrm)\ **Post date:** [January 30, 2026, 9:51am UTC](https://discuss.elastic.co/t/impact-of-cve-2025-68161-on-elasticsearch-v7-17-28/384825/1 "2026-01-30T09:51:16Z")
Hi, Kindly let know if **Elasticsearch v7.17.28** is impacted by **CVE-2025-68161** CVE Details as follows - Description: The **Socket Appender** in **Apache Log4j Core versions 2.0-beta9 through 2.25.2** does not perform TLS hostname verification of the peer certificate, even when the verifyHostName configuration attribute or the log4j2.sslVerifyHostName system property is set to true. This issue may allow a man-in-the-middle attacker to intercept or redirect log traffic under the following conditions: \* The attacker is able to intercept or redirect network traffic between the client and the log receiver. \* The attacker can present a server certificate issued by a certification authority trusted by the Socket Appender’s configured trust store (or by the default Java trust store if no custom trust store is configured). Users are advised to upgrade to Apache Log4j Core version 2.25.3, which addresses this issue. As an alternative mitigation, the Socket Appender may be configured to use a private or restricted trust root to limit the set of trusted certificates. Thank you. ---
**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, 9:53am UTC](https://discuss.elastic.co/t/impact-of-cve-2025-68161-on-elasticsearch-v7-17-28/384825/2 "2026-01-30T09:53:58Z")
Hi @amolrm, I would recommend reaching out to [security@elastic.co](mailto:security@elastic.co) with any security related queries. As an aside, 7.17 reached end of support earlier this month (see [here](https://www.elastic.co/support/eol#:~:text=7.17.x,15%2DJan%2D2026)) so I would recommend upgrading to version 8 or 9. Hope that helps! Carly ---
**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")
@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! ---
**Author:** ![amolrm](https://avatars.discourse-cdn.com/v4/letter/a/e495f1/32.png) [@amolrm](https://discuss.elastic.co/u/amolrm)\ **Post date:** [January 30, 2026, 3:56pm UTC](https://discuss.elastic.co/t/impact-of-cve-2025-68161-on-elasticsearch-v7-17-28/384825/4 "2026-01-30T15:56:06Z")
Hi Carly, Thank you for your repsone. The purpose behind the follow-up question was to know beforehand whether the suggested ES upgrade (to 8.x or 9.x) is immune to the vulnerability. If not, there would have been no point performing a immediate upgrade. Regards. ---
**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:** [January 30, 2026, 4:31pm UTC](https://discuss.elastic.co/t/impact-of-cve-2025-68161-on-elasticsearch-v7-17-28/384825/5 "2026-01-30T16:31:48Z")
> [@amolrm](#): > > If not, there would have been no point performing a immediate upgrade. There are multiple other CVEs affecting version 7, which is not supported anymore and wil not receive any fix. You can check the [Security Announcements](https://discuss.elastic.co/c/announcements/security-announcements/31).