Vulnerability Database · Go · Package report

github.com/go-ldap/ldap: vulnerability history, versions and safety

github.com/go-ldap/ldap is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 120 releases, from Feb 2022 to Aug 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on github.com/go-ldap/ldap v3.4.15+incompatible i

Updated on 22 Oct 2026

Action needed: v3.4.15+incompatible has 2 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 84/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release v3.4.15+incompatible — affected i
  • Vulnerabilities on record 2 over 2 years · 0 in the last year i
  • Latest disclosure 21 Aug 2024 i
  • Highest CVSS 8.1 i
  • With no published fix 0 i
  • Stars 2,461 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence MIT 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/go-ldap/ldap, 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.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v2.5.1-0.20261007184258-e614cf998727+incompatible 07 Oct 2026 H1 U1 MIT Yes Details →
v3.4.15+incompatible 07 Oct 2026 H1 U1 MIT Yes Details →
v2.5.1-0.20260928211947-f8db69e5ab80+incompatible 28 Sep 2026 H1 U1 MIT Yes Details →
v2.5.1-0.20260925135007-05f305f2813d+incompatible 25 Sep 2026 H1 U1 MIT Yes Details →
v2.5.1-0.20260907211324-2f8603fc1df3+incompatible 07 Sep 2026 H1 U1 MIT Yes Details →
v2.5.1-0.20260820200047-d59c822aa7f1+incompatible 20 Aug 2026 H1 U1 MIT Yes Details →
v2.5.1-0.20260810215616-56dc6fe26c57+incompatible 10 Aug 2026 H1 U1 MIT Yes Details →
v2.5.1-0.20260716005014-9e343e2ad186+incompatible 16 Jul 2026 H1 U1 MIT Yes Details →
v3.4.14+incompatible 16 Jul 2026 H1 U1 MIT Yes Details →
v2.5.1-0.20260715232813-c381fd487f74+incompatible 15 Jul 2026 H1 U1 MIT Yes Details →
v2.5.1-0.20260712223856-d6d6b04af606+incompatible 12 Jul 2026 H1 U1 MIT Yes Details →
v2.5.1-0.20260706165055-c90b197a99d8+incompatible 06 Jul 2026 H1 U1 MIT Yes Details →
v2.5.1-0.20260621194642-8a98971a72ca+incompatible 21 Jun 2026 H1 U1 MIT Yes Details →
v2.5.1-0.20260617152125-0da234d6be86+incompatible 17 Jun 2026 H1 U1 MIT Yes Details →
v2.5.1-0.20260614181102-46d38232425a+incompatible 14 Jun 2026 H1 U1 MIT Yes Details →
v2.5.1-0.20260609211628-c86c2e229cce+incompatible 09 Jun 2026 H1 U1 MIT Yes Details →
v2.5.1-0.20260523112508-e6320040345e+incompatible 23 May 2026 H1 U1 MIT Yes Details →
v2.5.1-0.20260517181707-5877c85234a6+incompatible 17 May 2026 H1 U1 MIT Yes Details →
v2.5.1-0.20260423230400-bf231eb99269+incompatible 23 Apr 2026 H1 U1 MIT Yes Details →
v2.5.1-0.20260404175526-5937e979b628+incompatible 04 Apr 2026 H1 U1 MIT Yes Details →
v2.5.1-0.20260301092458-3bbbfb11ea21+incompatible 01 Mar 2026 H1 U1 MIT Yes Details →
v3.4.13+incompatible 01 Mar 2026 H1 U1 MIT Yes Details →
v2.5.1-0.20260212215716-539d8f570b22+incompatible 12 Feb 2026 H1 U1 MIT Yes Details →
v2.5.1-0.20260212000640-570560be831a+incompatible 12 Feb 2026 H1 U1 MIT Yes Details →
v2.5.1-0.20260205214251-8bb1a965ebb3+incompatible 05 Feb 2026 H1 U1 MIT Yes Details →
v2.5.1-0.20260205203751-dbef7bed8558+incompatible 05 Feb 2026 H1 U1 MIT Yes Details →
v2.5.1-0.20251214211915-0935f925360d+incompatible 14 Dec 2025 H1 U1 MIT Yes Details →
v3.4.13-0.20251214211915-0935f925360d+incompatible 14 Dec 2025 H1 U1 MIT Yes Details →
v2.5.1-0.20251119232833-7db655e1802d+incompatible 19 Nov 2025 H1 U1 MIT Yes Details →
v2.5.1-0.20251109200052-e93db19c9f49+incompatible 09 Nov 2025 H1 U1 MIT Yes Details →
v2.5.1-0.20251101090757-b693143e97d2+incompatible 01 Nov 2025 H1 U1 MIT Yes Details →
v2.5.1-0.20251001135701-97082cc14c15+incompatible 01 Oct 2025 H1 U1 MIT Yes Details →
v3.4.12+incompatible 01 Oct 2025 H1 U1 MIT Yes Details →
v2.5.1-0.20250930204328-ad3fa743ce77+incompatible 30 Sep 2025 H1 U1 MIT Yes Details →
v2.5.1-0.20250908222514-82fef14a4694+incompatible 08 Sep 2025 H1 U1 MIT Yes Details →
v2.5.1-0.20250629104647-06d7bd93b868+incompatible 29 Jun 2025 H1 U1 MIT Yes Details →
v2.5.1-0.20250520221411-bab0be501db4+incompatible 20 May 2025 H1 U1 MIT Yes Details →
v2.5.1-0.20250513101145-109b1fc3f0cc+incompatible 13 May 2025 H1 U1 MIT Yes Details →
v2.5.1-0.20250511125916-0c1c6ca95d80+incompatible 11 May 2025 H1 U1 MIT Yes Details →
v2.5.1-0.20250414210932-e80f029a8185+incompatible 14 Apr 2025 H1 U1 MIT Yes Details →
v3.4.11+incompatible 14 Apr 2025 H1 U1 MIT Yes Details →
v2.5.1-0.20250407185144-d1298fcf754b+incompatible 07 Apr 2025 H1 U1 MIT Yes Details →
v2.5.1-0.20250306224916-ac1bc555291e+incompatible 06 Mar 2025 H1 U1 MIT Yes Details →
v2.5.1-0.20250221200958-b7e97bbe6084+incompatible 21 Feb 2025 H1 U1 MIT Yes Details →
v2.5.1-0.20250219223213-32469eb33488+incompatible 19 Feb 2025 H1 U1 MIT Yes Details →
v2.5.1-0.20250219221754-403d46a3a295+incompatible 19 Feb 2025 H1 U1 MIT Yes Details →
v2.5.1-0.20250218151432-d10ea4b7fb74+incompatible 18 Feb 2025 H1 U1 MIT Yes Details →
v2.5.1-0.20250110131057-5d1b644709df+incompatible 10 Jan 2025 H1 U1 MIT Yes Details →
v2.5.1-0.20241226220707-aebc65e39b4d+incompatible 26 Dec 2024 H1 U1 MIT Yes Details →
v3.4.10+incompatible 26 Dec 2024 H1 U1 MIT Yes Details →
v0.0.0-20241226191411-dc5f57d120a5 26 Dec 2024 H1 U1 MIT Yes Details →
v0.0.0-20241216122713-f71ace8fc571 16 Dec 2024 H1 U1 MIT Yes Details →
v0.0.0-20241214231628-5f6693ace8f0 14 Dec 2024 H1 U1 MIT Yes Details →
v0.0.0-20241031145629-601814bc120d 31 Oct 2024 H1 U1 MIT Yes Details →
v0.0.0-20240820190646-25c2d4887969 20 Aug 2024 H1 U1 MIT Yes Details →
v0.0.0-20240820093027-bc6bdd8fdaf4 20 Aug 2024 H1 U1 MIT Yes Details →
v0.0.0-20240528173651-dbdc48525944 28 May 2024 H1 U1 MIT Yes Details →
v0.0.0-20240503161532-56e5759aadc4 03 May 2024 H1 U1 MIT Yes Details →
v0.0.0-20240422164117-17409dc22c21 22 Apr 2024 H1 U1 MIT Yes Details →
v0.0.0-20240419171224-d170cda114a1 19 Apr 2024 H1 U1 MIT Yes Details →
v0.0.0-20240419170316-73de7585cfca 19 Apr 2024 H1 U1 MIT Yes Details →
v0.0.0-20240412095121-06d50d1ad03b 12 Apr 2024 H1 U1 MIT Yes Details →
v0.0.0-20240407093623-22600126bef6 07 Apr 2024 H1 U1 MIT Yes Details →
v0.0.0-20240406222600-9c1418558c73 06 Apr 2024 H1 U1 MIT Yes Details →
v0.0.0-20240402173119-4ca7b8eb2c3b 02 Apr 2024 H1 U1 MIT Yes Details →
v0.0.0-20240401202521-191cca8e766f 01 Apr 2024 H1 U1 MIT Yes Details →
v0.0.0-20240401170029-450e034c75dd 01 Apr 2024 H1 U1 MIT Yes Details →
v0.0.0-20240401083118-87d782bf238c 01 Apr 2024 H1 U1 MIT Yes Details →
v0.0.0-20240322185655-d13d063a5d39 22 Mar 2024 H1 U1 MIT Yes Details →
v0.0.0-20240314174501-83a306c8f13f 14 Mar 2024 H1 U1 MIT Yes Details →
v0.0.0-20240211173111-25b14db0ff3f 11 Feb 2024 H1 U1 MIT Yes Details →
v0.0.0-20240128123636-2d1e4dbeced8 28 Jan 2024 H1 U1 MIT Yes Details →
v0.0.0-20240113111401-90237880155c 13 Jan 2024 H1 U1 MIT Yes Details →
v0.0.0-20231218221713-a0fbbb246bfb 18 Dec 2023 H1 U1 MIT Yes Details →
v0.0.0-20231218220818-15fcefaca31c 18 Dec 2023 H1 U1 MIT Yes Details →
v0.0.0-20231211211558-cdbbc302b007 11 Dec 2023 H1 U1 MIT Yes Details →
v0.0.0-20231121002303-f02128188b70 21 Nov 2023 H1 U1 MIT Yes Details →
v0.0.0-20230916115147-21d1415bcac3 16 Sep 2023 H1 U1 MIT Yes Details →
v0.0.0-20230915143459-80095a39b534 15 Sep 2023 H1 U1 MIT Yes Details →
v0.0.0-20230915122112-03cc78cedc56 15 Sep 2023 H1 U1 MIT Yes Details →
v0.0.0-20230914182342-81e9beba4abb 14 Sep 2023 H1 U1 MIT Yes Details →
v0.0.0-20230907084633-07d2e0970536 07 Sep 2023 H1 U1 MIT Yes Details →
v0.0.0-20230906122243-5a8863bb057d 06 Sep 2023 H1 U1 MIT Yes Details →
v0.0.0-20230817104808-7f97b823a59b 17 Aug 2023 H1 U1 MIT Yes Details →
v0.0.0-20230810170403-bbc2f21fcbd7 10 Aug 2023 H1 U1 MIT Yes Details →
v0.0.0-20230808191127-a926d97d0209 08 Aug 2023 H1 U1 MIT Yes Details →
v0.0.0-20230805155059-36463555bb76 05 Aug 2023 H1 U1 MIT Yes Details →
v0.0.0-20230805154520-9306baec4849 05 Aug 2023 H1 U1 MIT Yes Details →
v0.0.0-20230722083820-d85ebd1d6518 22 Jul 2023 H1 U1 MIT Yes Details →
v0.0.0-20230630211630-7778a1cc2ef0 30 Jun 2023 H1 U1 MIT Yes Details →
v0.0.0-20230521105649-cdb0754f6668 21 May 2023 H1 U1 MIT Yes Details →
v0.0.0-20230506142018-039466e6b835 06 May 2023 H1 U1 MIT Yes Details →
v0.0.0-20230505180221-b50d28961f34 05 May 2023 H1 U1 MIT Yes Details →
v0.0.0-20230430114203-b0d0dcfc492e 30 Apr 2023 H1 U1 MIT Yes Details →
v0.0.0-20230405011012-83b8f3195696 05 Apr 2023 H1 U1 MIT Yes Details →
v0.0.0-20230405005734-6a543b2cd747 05 Apr 2023 H1 U1 MIT Yes Details →
v0.0.0-20230327113050-32d292ef5ded 27 Mar 2023 H1 U1 MIT Yes Details →
v0.0.0-20230308075704-6668c067894c 08 Mar 2023 H1 U1 MIT Yes Details →
v0.0.0-20230226130424-b64a808c288f 26 Feb 2023 H1 U1 MIT Yes Details →
v0.0.0-20230222001723-a79fb6b6eb9c 22 Feb 2023 H1 U1 MIT Yes Details →
v0.0.0-20230210083308-d16fb563008d 10 Feb 2023 H1 U1 — Yes Details →
v0.0.0-20230209072803-fe9154281c5a 09 Feb 2023 H1 U1 — Yes Details →
v0.0.0-20221212200739-0e43630234df 12 Dec 2022 H1 U1 — Yes Details →
v0.0.0-20221021183900-360012be3884 21 Oct 2022 H1 U1 — Yes Details →
v0.0.0-20221015081704-93825e993f83 15 Oct 2022 H1 U1 — Yes Details →
v0.0.0-20220806122933-c7248aadbf1f 06 Aug 2022 H1 U1 — Yes Details →
v0.0.0-20220726192148-cb504ae2f520 26 Jul 2022 H1 U1 — Yes Details →
v0.0.0-20220722093112-c4ad4d4beca2 22 Jul 2022 H1 U1 — Yes Details →
v0.0.0-20220720172922-f78b5acc5fab 20 Jul 2022 H1 U1 — Yes Details →
v0.0.0-20220627202100-83b05cd093e4 27 Jun 2022 H1 U1 — Yes Details →
v0.0.0-20220622184944-05f81f7abe37 22 Jun 2022 H1 U1 — Yes Details →
v0.0.0-20220605193032-a3dcdda8f127 05 Jun 2022 H1 U1 — Yes Details →
v0.0.0-20220425165149-7d3b8d48feec 25 Apr 2022 H1 U1 — Yes Details →
v0.0.0-20220425123424-f5d763664692 25 Apr 2022 H1 U1 — Yes Details →
v0.0.0-20220421132556-898ed3e692b7 21 Apr 2022 H1 U1 — Yes Details →
v0.0.0-20220421131511-f4d6fa9e8ae7 21 Apr 2022 H1 U1 — Yes Details →
v0.0.0-20220406183305-9b507edb833e 06 Apr 2022 H1 U1 — Yes Details →
v0.0.0-20220406170457-8c6415ac9035 06 Apr 2022 H1 U1 — Yes Details →
v0.0.0-20220406011036-62171265177c 06 Apr 2022 H1 U1 — Yes Details →
v0.0.0-20220104194136-13008e4c5260 04 Jan 2022 H1 U1 — Yes Details →

The newest 120 of 427 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2024 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for github.com/go-ldap/ldap

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About github.com/go-ldap/ldap

Is github.com/go-ldap/ldap safe to use?

Vulert records 2 vulnerabilities for github.com/go-ldap/ldap in Go: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is github.com/go-ldap/ldap's Vulert package health score?

Vulert scores github.com/go-ldap/ldap 84/100, which reads as in good shape. 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/go-ldap/ldap affected?

Yes. v3.4.15+incompatible, the version you would install today, has 2 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of github.com/go-ldap/ldap should I use?

v3.4.15+incompatible 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/go-ldap/ldap have?

2 vulnerabilities are recorded for github.com/go-ldap/ldap in the Go ecosystem: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/go-ldap/ldap vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/go-ldap/ldap in the last 12 months, and the oldest entry in this database dates to 15 Feb 2022. 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/go-ldap/ldap 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/go-ldap/ldap for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/go-ldap/ldap version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.