VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

pycel: vulnerability history, versions and safety

pycel is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 25 releases, first recorded in Apr 2025. 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
2 with no fix published

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

See the unfixed vulnerabilities →
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 pycel vulnerabilities

Vulert verdict on pycel 1.0.0b30 i

Updated on 23 Oct 2026

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

Package health score 42/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Little adoption
  • Community Inactive

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 1.0.0b30 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 17 Apr 2025 i
  • Highest CVSS 9.8 i
  • With no published fix 2 i
  • Depended on by 1 packages i
  • Stars 31 i
  • OpenSSF scorecard 1/10 i
  • Last release 60 months ago i
  • Licence GPL-3.0 i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 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 pycel, 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
1.0.0b30 13 Oct 2021 H1 U1 GPL-3.0 No Details →
1.0.0b29 13 Sep 2021 H1 U1 GPL-3.0 No Details →
1.0.0b28 31 Aug 2021 H1 U1 GPL-3.0 No Details →
1.0.0b27 11 Jul 2021 H1 U1 GPL-3.0 No Details →
1.0.0b26 18 Jun 2021 H1 U1 GPL-3.0 No Details →
1.0.0b22 18 Oct 2019 H1 U1 GPL-3.0 No Details →
1.0.0b21 14 Oct 2019 H1 U1 GPL-3.0 No Details →
1.0.0b20 23 Sep 2019 H1 U1 GPL-3.0 No Details →
1.0.0b19 12 Sep 2019 H1 U1 GPL-3.0 No Details →
1.0.0b18 08 Sep 2019 H1 U1 GPL-3.0 No Details →
1.0.0b17 03 Sep 2019 H1 U1 GPL-3.0 No Details →
1.0.0b16 08 Jul 2019 H1 U1 GPL-3.0 No Details →
1.0.0b15 30 Jun 2019 H1 U1 GPL-3.0 No Details →
1.0.0b14 16 Jun 2019 H1 U1 GPL-3.0 No Details →
1.0.0b13 11 May 2019 H1 U1 GPL-3.0 No Details →
1.0.0b12 23 Apr 2019 H1 U1 GPL-3.0 No Details →
1.0.0b11 21 Apr 2019 H1 U1 GPL-3.0 No Details →
1.0.0b8 21 Mar 2019 H1 U1 GPL-3.0 No Details →
1.0.0b7 10 Mar 2019 H1 U1 GPL-3.0 No Details →
1.0.0b6 04 Mar 2019 H1 U1 GPL-3.0 No Details →
1.0.0b5 24 Feb 2019 H1 U1 GPL-3.0 No Details →
1.0.0b4 17 Feb 2019 H1 U1 GPL-3.0 No Details →
1.0.0b3 02 Feb 2019 H1 U1 GPL-3.0 No Details →
1.0.0b2 06 Jan 2019 H1 U1 GPL-3.0 No Details →
1.0.0b0 25 Dec 2018 H1 U1 GPL-3.0 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 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 pycel

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-53924: Pycel Code Execution Vulnerability via Crafted Formulas 9.8 critical No fix published 17 Apr 2025
CVE-2024-53924: Pycel Code Injection Vulnerability via Crafted Formulas 8.9 high No fix published 17 Apr 2025

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 pycel

Is pycel safe to use?

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

What is pycel's Vulert package health score?

Vulert scores pycel 42/100, which reads as risky. 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 pycel affected?

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

How many vulnerabilities does pycel have?

2 vulnerabilities are recorded for pycel 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 pycel vulnerabilities disclosed?

0 vulnerabilities were recorded for pycel in the last 12 months, and the oldest entry in this database dates to 17 Apr 2025. 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 pycel 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 pycel for upcoming vulnerabilities?

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