Vulnerability Database · Go · Package report
github.com/elastic/go-elasticsearch: vulnerability history, versions and safety
github.com/elastic/go-elasticsearch is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the Go ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on github.com/elastic/go-elasticsearch v0.0.0 i
Updated on 23 Oct 2026
Good news: v0.0.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Key ecosystem project
- Community Moderate
What to do: Stay on v0.0.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 6,068 i
- OpenSSF scorecard 4/10 i
- Last release 92 months ago i
- Licence Apache-2.0 i
Version list, release dates, licence and dependants published by the Go module proxy, refreshed 23 Oct 2026. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Versions
Which versions are affected
Every version Vulert tracks for github.com/elastic/go-elasticsearch, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.
- v0.0.0-20190408091745-ea0edfe5b95f 08 Apr 2019
- v0.0.0-20190408085912-9247b7e60f05 08 Apr 2019
- v0.0.0-20190408083429-6211c3db3075 08 Apr 2019
- v0.0.0-20190407092831-6afbbb37e262 07 Apr 2019
- v0.0.0-20190407092816-70dd02ac2ea9 07 Apr 2019
- v0.0.0-20190407092644-3fb2a278216b 07 Apr 2019
- v0.0.0-20190402142442-ee3c672b25e5 02 Apr 2019
- v0.0.0-20190325180926-13d8ee1c440e 25 Mar 2019
- v0.0.1-0.20190325173100-2dfd38aab5eb 25 Mar 2019
- v0.0.0-20190325092138-89809b77718f 25 Mar 2019
- v0.0.0-20190324153251-956397d70b3d 24 Mar 2019
- v0.0.0-20190324084750-ec8c147b59fb 24 Mar 2019
- v0.0.0-20190316081522-60ea51fd3784 16 Mar 2019
- v0.0.0-20190315165114-3eda96823c81 15 Mar 2019
- v0.0.0-20190213111531-144b86dc76da 13 Feb 2019
- v0.0.1-0.20190213111531-144b86dc76da 13 Feb 2019
- v0.0.0 08 Feb 2019
- v0.0.0-20190208094730-3aa68f5e96e1 08 Feb 2019
- v0.0.0-20190208092403-0b599b97abe0 08 Feb 2019
- v0.0.0-20181018092512-1f300c8c7300 18 Oct 2018
- v0.0.0-20170926135607-8d1b946718be 26 Sep 2017
- v0.0.0-20170608022403-d4a08955f124 08 Jun 2017
All 22 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.
02 Disclosure history
How often vulnerabilities are recorded
No dated vulnerabilities are recorded for this package yet.
03 Vulnerabilities
Recorded vulnerabilities for github.com/elastic/go-elasticsearch
No vulnerabilities match this view.
Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback
Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315
Questions
About github.com/elastic/go-elasticsearch
Is github.com/elastic/go-elasticsearch safe to use?
Vulert has no vulnerabilities on record for github.com/elastic/go-elasticsearch in Go at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.
What is github.com/elastic/go-elasticsearch's Vulert package health score?
Vulert scores github.com/elastic/go-elasticsearch 65/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).
Is the latest version of github.com/elastic/go-elasticsearch affected?
No. v0.0.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.
Which version of github.com/elastic/go-elasticsearch should I use?
v0.0.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.
How many vulnerabilities does github.com/elastic/go-elasticsearch have?
0 vulnerabilities are recorded for github.com/elastic/go-elasticsearch in the Go ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.
How often are new github.com/elastic/go-elasticsearch vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/elastic/go-elasticsearch in the last 12 months. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.
Which versions of github.com/elastic/go-elasticsearch are affected?
Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.
How do I monitor github.com/elastic/go-elasticsearch for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/elastic/go-elasticsearch version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.