Vulnerability Database · Go · Package report
github.com/mdlayher/genetlink: vulnerability history, versions and safety
github.com/mdlayher/genetlink 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/mdlayher/genetlink v1.4.0 i
Updated on 23 Oct 2026
Good news: v1.4.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Niche
- Community Inactive
What to do: Stay on v1.4.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.4.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.4.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 67 i
- OpenSSF scorecard 3/10 i
- Last release 6 months ago 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/mdlayher/genetlink, 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.
- v1.4.0 31 Mar 2026
- v1.3.3-0.20260331163824-7ce858106b58 31 Mar 2026
- v0.0.0-20230429143659-7531bffe0f5e 29 Apr 2023
- v1.3.2 29 Apr 2023
- v1.3.2-0.20230429143659-7531bffe0f5e 29 Apr 2023
- v0.0.0-20221212131650-26d2658ab451 12 Dec 2022
- v1.3.1 12 Dec 2022
- v1.3.0 12 Nov 2022
- v1.2.1-0.20220213132639-3a2f76c62e40 13 Feb 2022
- v1.2.0 31 Jan 2022
- v1.1.1-0.20211213204928-386e281e56c6 13 Dec 2021
- v1.1.0 08 Dec 2021
- v1.0.0 14 Jan 2020
- v0.0.0-20191205172946-651acf4b47ef 05 Dec 2019
- v0.0.0-20191008151445-a2cadeac9a63 08 Oct 2019
- v0.0.0-20191004171646-5cf585d3b847 04 Oct 2019
- v0.0.0-20190828143517-e35f2bf499b9 28 Aug 2019
- v0.0.0-20190617154021-985b2115c31a 17 Jun 2019
- v0.0.0-20190614145742-9b59fb16384d 14 Jun 2019
- v0.0.0-20190605184957-3071ac0624c8 05 Jun 2019
- v0.0.0-20190513144241-4cdc5dab577c 13 May 2019
- v0.0.0-20190420033754-198ed5902e0b 20 Apr 2019
- v0.0.0-20190419142426-b806ce69960a 19 Apr 2019
- v0.0.0-20190411154927-2d43e79ece49 11 Apr 2019
- v0.0.0-20190405145436-b0a98e0cf7c0 05 Apr 2019
- v0.0.0-20190405143558-926589392914 05 Apr 2019
- v0.0.0-20190403191428-2f1f2342ea34 03 Apr 2019
- v0.0.0-20190313224034-60417448a851 13 Mar 2019
- v0.0.0-20190312142348-0653e1f008f9 12 Mar 2019
- v0.0.0-20190301202436-f9c7bfa6f0ae 01 Mar 2019
- v0.0.0-20190301202039-8ebac1f97bd7 01 Mar 2019
- v0.0.0-20190301155031-8917356f3e0f 01 Mar 2019
- v0.0.0-20181016160152-e97704c1b795 16 Oct 2018
- v0.0.0-20180917171408-7615bc153978 17 Sep 2018
- v0.0.0-20180728170340-ca85b5a30744 28 Jul 2018
- v0.0.0-20180728165928-ff2f7a32bc0d 28 Jul 2018
- v0.0.0-20180728165707-101eb22de852 28 Jul 2018
- v0.0.0-20180727163734-2f5bf8f12069 27 Jul 2018
- v0.0.0-20180721192401-71670317917e 21 Jul 2018
- v0.0.0-20180704154118-2806253bd5d0 04 Jul 2018
- v0.0.0-20180523153618-0b18675c0b77 23 May 2018
- v0.0.0-20170901181924-76fecce4c787 01 Sep 2017
All 42 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/mdlayher/genetlink
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/mdlayher/genetlink
Is github.com/mdlayher/genetlink safe to use?
Vulert has no vulnerabilities on record for github.com/mdlayher/genetlink 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/mdlayher/genetlink's Vulert package health score?
Vulert scores github.com/mdlayher/genetlink 68/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/mdlayher/genetlink affected?
No. v1.4.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/mdlayher/genetlink should I use?
v1.4.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/mdlayher/genetlink have?
0 vulnerabilities are recorded for github.com/mdlayher/genetlink 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/mdlayher/genetlink vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/mdlayher/genetlink 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/mdlayher/genetlink 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/mdlayher/genetlink for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/mdlayher/genetlink version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.