Vulnerability Database · Go · Package report

github.com/linkerd/linkerd2: vulnerability history, versions and safety

github.com/linkerd/linkerd2 is a package in the Go ecosystem. Vulert records 3 vulnerabilities for it across 120 releases, from Jul 2024 to May 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded M1 U2
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
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/linkerd/linkerd2 v18.9.1+incompatible i

Updated on 23 Oct 2026

Careful: one of the 3 vulnerabilities Vulert records for this package has no fix yet. Plan around that one, or apply its workaround. The rest have a fixed version to move to.

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

What to do: Plan around the 1 vulnerability with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release v18.9.1+incompatible — unaffected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 20 May 2025 i
  • Highest CVSS 6.5 i
  • With no published fix 1 i
  • Stars 11,516 i
  • OpenSSF scorecard 7/10 i
  • Last release this month 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/linkerd/linkerd2, 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
v0.5.1-0.20261020160834-5bb8ea8434bb 20 Oct 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20261015221148-b60b8e74786e 15 Oct 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20261015212930-2783b45768d6 15 Oct 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20261008235134-28fefed6669b 08 Oct 2026 M1 U2 Apache-2.0 No Details →
v0.0.0-20261005165045-f6415cf0f2a6 05 Oct 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20261005165045-f6415cf0f2a6 05 Oct 2026 M1 U2 Apache-2.0 No Details →
v0.0.0-20261002162426-f0cb1f2c8a80 02 Oct 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20261002162426-f0cb1f2c8a80 02 Oct 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20261001222557-e7c15f3a6c93 01 Oct 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20261001004133-7065a67bb2b0 01 Oct 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260930233140-8f398ed9312b 30 Sep 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260930223742-93c2a7f0924f 30 Sep 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260930205152-7b1e55c8762a 30 Sep 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260925222103-6f9745867aba 25 Sep 2026 M1 U2 Apache-2.0 No Details →
v0.0.0-20260916192123-2245d16d3b2c 16 Sep 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260916192123-2245d16d3b2c 16 Sep 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260914212738-4607bffec3d7 14 Sep 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260911150517-f7e12976baf9 11 Sep 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260904190334-2946a07088e1 04 Sep 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260904145556-bdfaad19c4c8 04 Sep 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260901171236-f178e2d31d0c 01 Sep 2026 M1 U2 Apache-2.0 No Details →
v0.0.0-20260826135829-399c6e336fc9 26 Aug 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260826135829-399c6e336fc9 26 Aug 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260825141108-960b692c3333 25 Aug 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260824181922-e41c08e62e59 24 Aug 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260821225255-b24cd4059841 21 Aug 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260821162827-19a0d90d5a4a 21 Aug 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260820222613-b80c292ee9f2 20 Aug 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260820214039-0b98319f8b4e 20 Aug 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260820144350-a9250f22c8fd 20 Aug 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260819163218-8c2e80cdf7c6 19 Aug 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260818220613-3ee3121e0202 18 Aug 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260812204504-2f74727508b7 12 Aug 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260811200020-57688337b481 11 Aug 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260804213849-e72a0478b09e 04 Aug 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260730191633-3af2f450ebf4 30 Jul 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260724153741-aded2e414ed7 24 Jul 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260723215141-88414c62846b 23 Jul 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260722141154-1877684d422f 22 Jul 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260716180353-59813f0e0530 16 Jul 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260715004824-e46260da9313 15 Jul 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260710162207-640c45614704 10 Jul 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260709163651-8c89e4973a51 09 Jul 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260708154634-c2561c27c07d 08 Jul 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260703144653-163123313952 03 Jul 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260702165831-137378a0c4b9 02 Jul 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260625162614-7c3782eb4a68 25 Jun 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260624142853-ae8300ba984b 24 Jun 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260622225159-eadc1acf79ad 22 Jun 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260618140033-7977d505fc3d 18 Jun 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260616145315-4d9df19afca4 16 Jun 2026 M1 U2 Apache-2.0 No Details →
v0.0.0-20260615155958-5861fb59158a 15 Jun 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260615155958-5861fb59158a 15 Jun 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260612141342-53a398472c38 12 Jun 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260608231546-3932dfa03ecb 08 Jun 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260605164929-69f22dd3aa0b 05 Jun 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260604162103-d7980d6d737f 04 Jun 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260602161456-3c65384aa227 02 Jun 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260529205719-e36e9e1bcf72 29 May 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260528205907-153bd80d247c 28 May 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260522163430-4c7417d68031 22 May 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260520155811-17566db77af3 20 May 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260515142927-3e3e78729233 15 May 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260502012340-b781ecf0c862 02 May 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260429212408-f37b69d2f655 29 Apr 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260423183538-811943c39085 23 Apr 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260420211630-9e25fc584252 20 Apr 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260415172610-8ca8bbcfdc58 15 Apr 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260409193643-cda7b5cbafb5 09 Apr 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260408151207-b0431fde84c0 08 Apr 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260402204901-372abd361635 02 Apr 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260327142043-9099be0d2dbd 27 Mar 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260326002935-00344cfe0301 26 Mar 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260320151349-f3311c7391ef 20 Mar 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260319182509-035f253d7917 19 Mar 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260313182004-b62d23b1fac4 13 Mar 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260312003141-806fc552f8e6 12 Mar 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260306173744-2e1f10c11928 06 Mar 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260305235702-2534d7d3702e 05 Mar 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260304221444-48ceb7e2b598 04 Mar 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260226225947-a782232ad4d9 26 Feb 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260225161533-e9f40d656505 25 Feb 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260225133715-0c397e6a76be 25 Feb 2026 M1 U2 Apache-2.0 No Details →
v0.0.0-20260219003652-2ab0dd68f999 19 Feb 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260219003652-2ab0dd68f999 19 Feb 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260217191736-b5621f5c07d8 17 Feb 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260129150856-8b195475018a 29 Jan 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260122141415-f5170ecc650c 22 Jan 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260114233805-7ae1c1f1b49e 14 Jan 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260114144520-a2b1189358ba 14 Jan 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20260106143553-d22fbc715226 06 Jan 2026 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20251223175734-aae22baf5684 23 Dec 2025 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20251222072645-e644230bdeb3 22 Dec 2025 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20251218125401-5ab8100bff33 18 Dec 2025 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20251210171321-468ce74aa236 10 Dec 2025 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20251209171501-f512b6061798 09 Dec 2025 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20251204210654-7a1a06cb8d91 04 Dec 2025 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20251127145753-7af543798764 27 Nov 2025 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20251126204810-b5d6661b9e82 26 Nov 2025 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20251120143450-91df29954411 20 Nov 2025 M1 U2 Apache-2.0 No Details →
v0.5.1-0.20251119141514-b699ea721c3f 19 Nov 2025 M1 U2 — No Details →
v0.5.1-0.20251113194902-68c8969d295b 13 Nov 2025 M1 U2 — No Details →
v0.5.1-0.20251112223036-9bb223c4472e 12 Nov 2025 M1 U2 — No Details →
v0.5.1-0.20251107173009-76e274fd1ab0 07 Nov 2025 M1 U2 — No Details →
v0.5.1-0.20251106191711-8dca48411146 06 Nov 2025 M1 U2 — No Details →
v0.5.1-0.20251030143746-234c679c00b9 30 Oct 2025 M1 U2 — No Details →
v0.5.1-0.20251029215008-0ebd74b02665 29 Oct 2025 M1 U2 — No Details →
v0.5.1-0.20251023162342-f8faaecc1a5c 23 Oct 2025 M1 U2 — No Details →
v0.5.1-0.20251022141442-8be7f16b48ef 22 Oct 2025 M1 U2 — No Details →
v0.5.1-0.20251020142143-f98fc6ac4324 20 Oct 2025 M1 U2 — No Details →
v0.5.1-0.20251016154546-83181ba71352 16 Oct 2025 M1 U2 — No Details →
v0.5.1-0.20251013225055-834b32ecedcf 13 Oct 2025 M1 U2 — No Details →
v0.5.1-0.20251010135246-438533902011 10 Oct 2025 M1 U2 — No Details →
v0.5.1-0.20251009182857-291660dd5bfd 09 Oct 2025 M1 U2 — No Details →
v0.5.1-0.20251007224401-d3788f6a66d7 07 Oct 2025 M1 U2 — No Details →
v0.0.0-20251003185759-575de3428744 03 Oct 2025 M1 U2 — No Details →
v0.5.1-0.20251003185759-575de3428744 03 Oct 2025 M1 U2 — No Details →
v0.5.1-0.20251001204414-a19210aa5ff2 01 Oct 2025 M1 U2 — No Details →
v0.5.1-0.20250930174528-75fe78b5c074 30 Sep 2025 M1 U2 — No Details →
v0.5.1-0.20250925155235-50801b2c1d00 25 Sep 2025 M1 U2 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1
  • 2025 2

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/linkerd/linkerd2

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 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: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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/linkerd/linkerd2

Is github.com/linkerd/linkerd2 safe to use?

Vulert records 3 vulnerabilities for github.com/linkerd/linkerd2 in Go: 0 critical, 0 high, 1 medium and 0 low, plus 2 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is github.com/linkerd/linkerd2's Vulert package health score?

Vulert scores github.com/linkerd/linkerd2 92/100, which reads as healthy. 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).

Which version of github.com/linkerd/linkerd2 should I use?

v18.9.1+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/linkerd/linkerd2 have?

3 vulnerabilities are recorded for github.com/linkerd/linkerd2 in the Go ecosystem: 0 critical, 0 high, 1 medium and 0 low, plus 2 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/linkerd/linkerd2 vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/linkerd/linkerd2 in the last 12 months, and the oldest entry in this database dates to 22 Jul 2024. 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/linkerd/linkerd2 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/linkerd/linkerd2 for upcoming vulnerabilities?

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