Vulnerability Database · Go · Package report
github.com/bluenviron/gomavlib/v3: vulnerability history, versions and safety
github.com/bluenviron/gomavlib/v3 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/bluenviron/gomavlib/v3 v3.3.5 i
Updated on 23 Oct 2026
Good news: v3.3.5, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Niche
- Community Quiet
What to do: Stay on v3.3.5 or newer. This can change: a vulnerability disclosed tomorrow can affect v3.3.5 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v3.3.5 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 197 i
- OpenSSF scorecard 4/10 i
- Last release 4 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/bluenviron/gomavlib/v3, 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.
- v3.3.5 01 Jun 2026
- v3.3.4 20 May 2026
- v3.3.3 17 May 2026
- v3.3.2 16 May 2026
- v3.3.2-0.20260507060738-9e7197c0bced 07 May 2026
- v3.3.1 27 Apr 2026
- v3.3.1-0.20260402053944-051090d1c8f0 02 Apr 2026
- v3.3.1-0.20260318053721-b8c7a00dad10 18 Mar 2026
- v3.3.1-0.20251102114841-f5c64e6dc10e 02 Nov 2025
- v3.3.0 17 Oct 2025
- v3.2.1 14 Mar 2025
- v3.2.1-0.20250314205818-fef3864a0759 14 Mar 2025
- v3.2.1-0.20250314162600-2f374d98ed11 14 Mar 2025
- v3.2.0 12 Mar 2025
- v3.1.1-0.20250306113757-22162fb899f5 06 Mar 2025
- v3.1.1-0.20250305051948-a942c77df15c 05 Mar 2025
- v3.1.0 15 Dec 2024
- v3.0.1-0.20241209105705-e17b1c3ec63b 09 Dec 2024
- v3.0.1-0.20241208162611-4697bc66e8cf 08 Dec 2024
- v3.0.1-0.20241205052009-bd18fbc9cf17 05 Dec 2024
- v3.0.1-0.20241204051947-a63b96f26f0e 04 Dec 2024
- v3.0.1-0.20241203110129-967fc9d89193 03 Dec 2024
- v3.0.1-0.20241202135214-dedb40bbe23d 02 Dec 2024
- v3.0.1-0.20241125124213-2bbea7656f25 25 Nov 2024
- v3.0.1-0.20241121051922-013769aa1d83 21 Nov 2024
- v3.0.1-0.20241120051924-9f865a8fc92b 20 Nov 2024
- v3.0.1-0.20241114051852-abe57eaa225e 14 Nov 2024
- v3.0.1-0.20241107051811-a0b7119b85d2 07 Nov 2024
- v3.0.1-0.20240905051751-7b22f1111ffb 05 Sep 2024
- v3.0.0-20240814190713-11298893d07f 14 Aug 2024
- v3.0.1-0.20240705051614-2c23f88525d9 05 Jul 2024
- v3.0.1-0.20240508202640-12a247bf4798 08 May 2024
- v3.0.0 13 Apr 2024
- v3.0.0-20240413192159-d6b12ab30d26 13 Apr 2024
All 34 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/bluenviron/gomavlib/v3
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/bluenviron/gomavlib/v3
Is github.com/bluenviron/gomavlib/v3 safe to use?
Vulert has no vulnerabilities on record for github.com/bluenviron/gomavlib/v3 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/bluenviron/gomavlib/v3's Vulert package health score?
Vulert scores github.com/bluenviron/gomavlib/v3 71/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/bluenviron/gomavlib/v3 affected?
No. v3.3.5, 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/bluenviron/gomavlib/v3 should I use?
v3.3.5 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/bluenviron/gomavlib/v3 have?
0 vulnerabilities are recorded for github.com/bluenviron/gomavlib/v3 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/bluenviron/gomavlib/v3 vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/bluenviron/gomavlib/v3 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/bluenviron/gomavlib/v3 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/bluenviron/gomavlib/v3 for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/bluenviron/gomavlib/v3 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.