Vulnerability Database · Hex · Package report

cowlib: vulnerability history, versions and safety

cowlib is a package in the Hex ecosystem. Vulert records 11 vulnerabilities for it across 39 releases, from May 2026 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
11 vulnerabilities recorded H2 M1 L1 U7
i
5 with no fix published

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

See the unfixed vulnerabilities →
i
11 in the last 12 months

Most recent disclosure 18 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on cowlib 2.21.0 i

Updated on 23 Oct 2026

Careful: 2.21.0 has 5 known vulnerabilities, and 5 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 50/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Not enough data

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 2.21.0 — affected i
  • Vulnerabilities on record 11 over 1 year · 11 in the last year i
  • Latest disclosure 18 Aug 2026 i
  • Highest CVSS 8.7 i
  • With no published fix 5 i
  • Depended on by 106,871,198 packages i
  • Last release this month i

Version list, release dates, licence and dependants published by hex.pm, 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 cowlib, 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
2.21.0 08 Oct 2026 L1 U4 — No Details →
2.20.0 08 Sep 2026 L1 U4 — No Details →
2.19.0 28 Jul 2026 U1 — No Details →
2.18.0 02 Jul 2026 U2 — No Details →
2.17.1 11 Jun 2026 U2 — No Details →
2.17.0 08 Jun 2026 U3 — No Details →
2.16.1 12 May 2026 L1 U3 — No Details →
2.16.0 18 Sep 2025 H2 M1 L1 U7 — No Details →
2.15.0 11 Apr 2025 H2 M1 L1 U7 — No Details →
2.14.0 17 Feb 2025 H2 M1 L1 U7 — No Details →
2.13.0 14 Mar 2024 H2 M1 L1 U7 — No Details →
2.12.1 03 Apr 2023 H2 M1 L1 U7 — No Details →
2.12.0 16 Jan 2023 H2 M1 L1 U7 — No Details →
2.11.0 12 May 2021 H2 M1 L1 U7 — No Details →
2.10.1 19 Nov 2020 H2 M1 L1 U7 — No Details →
2.10.0 06 Nov 2020 H2 M1 L1 U7 — No Details →
2.9.1 28 May 2020 H2 M1 L1 U7 — No Details →
2.9.0 25 Mar 2020 H2 M1 L1 U7 — No Details →
2.8.0 16 Oct 2019 H2 M1 U4 — No Details →
2.7.3 05 Apr 2019 H2 M1 U4 — No Details →
2.7.2 04 Apr 2019 H2 M1 U4 — No Details →
2.7.1 03 Apr 2019 H2 M1 U4 — No Details →
2.7.0 17 Nov 2018 H2 M1 U4 — No Details →
2.6.0 18 Sep 2018 H2 M1 U4 — No Details →
2.5.1 19 Aug 2018 H2 U3 — Yes Details →
2.5.0 03 Aug 2018 H2 U3 — Yes Details →
2.4.0 05 Jul 2018 H2 U3 — Yes Details →
2.3.0 02 May 2018 H2 U3 — Yes Details →
2.2.1 28 Mar 2018 H2 U3 — Yes Details →
2.2.0 05 Mar 2018 H2 U3 — Yes Details →
2.1.0 13 Dec 2017 H2 U3 — Yes Details →
2.0.1 01 Nov 2017 H2 U3 — Yes Details →
2.0.0 05 Oct 2017 H2 U3 — Yes Details →
1.3.0 02 Jul 2015 H2 U2 — Yes Details →
1.2.0 02 Jul 2015 H2 U2 — Yes Details →
1.1.0 02 Jul 2015 H2 U2 — Yes Details →
1.0.2 16 Nov 2015 H2 U2 — Yes Details →
1.0.1 28 Dec 2014 H2 U2 — Yes Details →
1.0.0 01 Aug 2014 H2 U2 — Yes Details →

All 39 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 11

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

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 cowlib

Is cowlib safe to use?

Vulert records 11 vulnerabilities for cowlib in Hex: 0 critical, 2 high, 1 medium and 1 low, plus 7 not yet rated. 5 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is cowlib's Vulert package health score?

Vulert scores cowlib 50/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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of cowlib affected?

Yes. 2.21.0, the version you would install today, has 5 known vulnerabilities, and 5 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does cowlib have?

11 vulnerabilities are recorded for cowlib in the Hex ecosystem: 0 critical, 2 high, 1 medium and 1 low, plus 7 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 cowlib vulnerabilities disclosed?

11 vulnerabilities were recorded for cowlib in the last 12 months, and the oldest entry in this database dates to 11 May 2026. 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 cowlib 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 cowlib for upcoming vulnerabilities?

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