Database

OpenSearch: supported versions and open vulnerabilities today

OpenSearch 3 is supported; 2 has no announced end-of-life date but no active support; 1 reached end of life on May 6, 2025; the latest release is 3.9.0. No advisories for OpenSearch were published in the last 12 months.

Last checked against endoflife.date, OSV.dev and deps.dev.

Latest release
3.9.0
GitHub stars
13.9k
Licence
Apache-2.0

Supported versions

OpenSearch release lines and security support dates from endoflife.date
VersionSecurity supportLatestReleased
OpenSearch 3Supported: No end date announced3.9.0
OpenSearch 2No end-of-life date announced: No date announced; active support ended2.19.6
OpenSearch 1Ended: Ended 1.3.20

Security advisories

OSV.dev, CISA KEV and FIRST EPSS

No advisories published in the last 12 months. 1 in total since records began. Checked packages: org.opensearch:opensearch.

All org.opensearch:opensearch advisories on OSV.dev

Maintenance and supply chain

deps.dev has no OpenSSF Scorecard for this repository.

Source repository

Alternatives

  • Elasticsearch

    Distributed search and analytics engine

    Strengths

    • Powerful full-text search
    • Real-time indexing

    Trade-offs

    • High memory usage
    • Complex to tune and optimize
    Elasticsearch health today
  • Algolia

    Managed search and discovery API

    Strengths

    • Blazing fast search (<10ms)
    • Easy to implement

    Trade-offs

    • Vendor lock-in
    • Limited customization
  • Typesense

    Open-source alternative to Algolia

    Strengths

    • Fast search performance
    • Easy to set up

    Trade-offs

    • Smaller ecosystem
    • Fewer advanced features
  • Meilisearch

    Lightning-fast open-source search engine

    Strengths

    • Sub-millisecond search responses
    • Out-of-the-box typo tolerance

    Trade-offs

    • Less feature-rich than Elasticsearch
    • Single-node deployment (no clustering)
    Meilisearch health today

Check OpenSearch in your own stack

This page checks OpenSearch in general. Your repo pins specific versions: the free dependency check reads your manifests and lists what to fix first. Prism Agent runs the same live checks on your whole stack and turns them into a plan your coding agent can build.