Algolia vs Elasticsearch

The most recent visible output from Elastic is entirely security advisories — CVEs patched across Kibana (path traversal, authorization bypass, DoS), Fleet Server, Filebeat, and APM Server all published on the same day. This kind of dense advisory release typically follows a coordinated security audit rather than organic bug discovery. No feature releases appear in this window. Elastic continues shipping patches simultaneously across the 8.x and 9.x release lines.

Maintaining parallel 8.x and 9.x release branches means every security fix ships across multiple version trees, which signals that enterprise customers unable to migrate quickly are still a first-class consideration. The vulnerability classes concentrated in Fleet and Kibana's ML and Osquery features — path traversal, authorization scope gaps, unbounded allocation — suggest security audit attention has shifted toward the orchestration and observability layers rather than the core search engine. Whether this clears the backlog ahead of a feature release is not clear from entries alone.

A feature-bearing release is likely overdue given the all-maintenance cadence visible here. If Elastic is clearing the security backlog before a major announcement, a 9.6 or named feature release could follow. Without feature entries to triangulate on, the prediction is uncertain.