VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

codecov: vulnerability history, versions and safety

codecov is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 0 release, first recorded in Jul 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

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.

See all codecov vulnerabilities

Vulert verdict on codecov 2.1.13 i

Updated on 23 Oct 2026

Good news: 2.1.13, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 67/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Niche
  • Community Quiet

What to do: Stay on 2.1.13 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.1.13 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2.1.13 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 14 Jul 2022 i
  • Highest CVSS 6.5 i
  • With no published fix 0 i
  • Depended on by 172 packages i
  • Stars 184 i
  • OpenSSF scorecard 3/10 i
  • Last release 42 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by PyPI, 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 codecov, 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.1.13 17 Apr 2023 none Apache-2.0 — Details →
2.1.13-py3.8 — none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2

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

03 Vulnerabilities

Recorded vulnerabilities for codecov

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-10800: Codecov prior to 2.0.16 does not sanitize gcov arguments 6.5 high 2.0.16 14 Jul 2022
CVE-2019-10800: Vulnerability in codecov package N/A unrated 2a80aa434f74feb31242b6f213b75ce63ae97902 13 Jul 2022

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 codecov

Is codecov safe to use?

Vulert records 2 vulnerabilities for codecov in PyPI: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is codecov's Vulert package health score?

Vulert scores codecov 67/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 codecov affected?

No. 2.1.13, 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 codecov should I use?

2.1.13 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 codecov have?

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

0 vulnerabilities were recorded for codecov in the last 12 months, and the oldest entry in this database dates to 13 Jul 2022. 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 codecov 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 codecov for upcoming vulnerabilities?

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