Vulnerability Database · Go · Package report
github.com/caarlos0/env/v11: vulnerability history, versions and safety
github.com/caarlos0/env/v11 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/caarlos0/env/v11 v11.4.1 i
Updated on 23 Oct 2026
Good news: v11.4.1, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Key ecosystem project
- Community Moderate
What to do: Stay on v11.4.1 or newer. This can change: a vulnerability disclosed tomorrow can affect v11.4.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v11.4.1 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 6,340 i
- OpenSSF scorecard 5/10 i
- Last release 5 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/caarlos0/env/v11, 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.
- v11.4.2-0.20261007202121-c1b2429e2590 07 Oct 2026
- v11.4.2-0.20261002135734-505764460181 02 Oct 2026
- v11.4.2-0.20260904005930-fb6403538040 04 Sep 2026
- v11.4.2-0.20260902224910-6c3de6f047c2 02 Sep 2026
- v11.0.0-20260803163247-970ff84ff33e 03 Aug 2026
- v11.4.2-0.20260803163247-970ff84ff33e 03 Aug 2026
- v11.0.0-20260707022951-a3a36cc60fa2 07 Jul 2026
- v11.4.2-0.20260707022951-a3a36cc60fa2 07 Jul 2026
- v11.4.2-0.20260601193102-9625c9ef37e1 01 Jun 2026
- v11.0.0-20260501170122-a72d89a8930f 01 May 2026
- v11.4.1 01 May 2026
- v11.4.1-0.20260501170122-a72d89a8930f 01 May 2026
- v11.0.0-20260409013145-1ff55e6c9733 09 Apr 2026
- v11.3.1-0.20260409013145-1ff55e6c9733 09 Apr 2026
- v11.4.1-0.20260409013145-1ff55e6c9733 09 Apr 2026
- v11.4.1-0.20260401050753-0cb635b62488 01 Apr 2026
- v11.4.0 22 Feb 2026
- v11.3.2-0.20260216105636-c98ad844e1e4 16 Feb 2026
- v11.3.2-0.20251222100307-7b10cf56e20f 22 Dec 2025
- v11.3.2-0.20251208100309-7b5005693b54 08 Dec 2025
- v11.3.2-0.20251121115917-548a7a66c9d5 21 Nov 2025
- v11.3.2-0.20251114080252-304f1e140f6e 14 Nov 2025
- v11.3.2-0.20251110080326-e389ab38b06e 10 Nov 2025
- v11.3.2-0.20251031080315-ebe59d201927 31 Oct 2025
- v11.3.2-0.20251027082735-6854d95d1356 27 Oct 2025
- v11.3.2-0.20251024080343-df09243be8ff 24 Oct 2025
- v11.3.2-0.20251013081836-a268413f0b0d 13 Oct 2025
- v11.3.2-0.20251003080512-f29faf46f2b7 03 Oct 2025
- v11.3.2-0.20250929091444-e45219adff58 29 Sep 2025
- v11.3.2-0.20250904123314-e4c4f01d1b79 04 Sep 2025
- v11.3.2-0.20250812133607-09e4145b920f 12 Aug 2025
- v11.3.2-0.20250505082809-56a09d295d93 05 May 2025
- v11.3.2-0.20250325081752-0669e014efa1 25 Mar 2025
- v11.3.2-0.20250221130920-8917d78b4247 21 Feb 2025
- v11.3.2-0.20250221130903-2be9960e75cc 21 Feb 2025
- v11.3.1 20 Dec 2024
- v11.3.1-0.20241216112255-4ebfdad1c46f 16 Dec 2024
- v11.2.3-0.20241212131009-0cbf40b610ab 12 Dec 2024
- v11.3.0 12 Dec 2024
- v11.2.3-0.20241206023726-52e7186e71f6 06 Dec 2024
- v11.2.3-0.20241202131308-cb81472a5c49 02 Dec 2024
- v11.2.3-0.20241126151417-f68d1dcfe3bd 26 Nov 2024
- v11.2.3-0.20241115131012-a9fcfa336f5c 15 Nov 2024
- v11.2.3-0.20241021111956-e55230b50da8 21 Oct 2024
- v11.2.3-0.20241011192046-4ab8b371a1e3 11 Oct 2024
- v11.2.3-0.20241008174450-1cb1967ed199 08 Oct 2024
- v11.2.3-0.20240824162950-84c7739f7080 24 Aug 2024
- v11.2.2 07 Aug 2024
- v11.2.2-0.20240807125618-aa50469e8054 07 Aug 2024
- v11.2.1 07 Aug 2024
- v11.2.1-0.20240807121823-2683e95c8298 07 Aug 2024
- v11.2.1-0.20240807035257-12820420829d 07 Aug 2024
- v11.2.1-0.20240807032114-be1c262485af 07 Aug 2024
- v11.1.1-0.20240807010431-d7efb648b593 07 Aug 2024
- v11.1.1-0.20240719005245-68793c069669 19 Jul 2024
- v11.2.0 19 Jul 2024
- v11.1.1-0.20240701132410-0de93839a295 01 Jul 2024
- v11.0.2-0.20240619133752-432567cfba93 19 Jun 2024
- v11.1.0 19 Jun 2024
- v11.0.1 17 May 2024
- v11.0.1-0.20240517121422-c4db90963971 17 May 2024
- v11.0.0 16 Apr 2024
- v11.0.0-20240416125223-4723331e0b43 16 Apr 2024
All 63 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/caarlos0/env/v11
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/caarlos0/env/v11
Is github.com/caarlos0/env/v11 safe to use?
Vulert has no vulnerabilities on record for github.com/caarlos0/env/v11 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/caarlos0/env/v11's Vulert package health score?
Vulert scores github.com/caarlos0/env/v11 83/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/caarlos0/env/v11 affected?
No. v11.4.1, 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/caarlos0/env/v11 should I use?
v11.4.1 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/caarlos0/env/v11 have?
0 vulnerabilities are recorded for github.com/caarlos0/env/v11 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/caarlos0/env/v11 vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/caarlos0/env/v11 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/caarlos0/env/v11 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/caarlos0/env/v11 for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/caarlos0/env/v11 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.