




Version 7.17.20 of the Elastic Stack was released today. We recommend you upgrade to this latest version. We recommend 7.17.20 over the previous version 7.17.19.
The7.17.20 patch release contains a fix for a bug in JDK22 in 7.17.19 release. This bug causes Elasticsearch nodes to crash, as well as, causing data corruption. The current workaround is to downgrade 7.17.19 to JDK.21.0.2
For details of the issues that have been fixed and



Version 8.13.2 of the Elastic Stack was released today. We recommend you upgrade to this latest version. We recommend 8.13.2 over the previous versions 8.13.1 and 8.13.0.
The 8.13.2 patch release contains a fix for a bug in JDK22 in both 8.13 and 8.13.1 releases. This bug causes Elasticsearch nodes to crash, as well as, causing data corruption. The current workaround is to downgrade both 8.13 and 8.13.1 to JDK.21.0.2
This patch rele
