VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

cron: vulnerability history, versions and safety

cron is a package in the Debian ecosystem. Vulert records 10 vulnerabilities for it across 3 affected ranges, from May 2006 to Mar 2019. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
10 vulnerabilities recorded U10
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 cron vulnerabilities

Vulert verdict on cron i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 12 Mar 2019. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 10 vulnerabilities on record across 12 years, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 10 over 12 years · 0 in the last year i
  • Latest disclosure 12 Mar 2019 i
  • Highest CVSS 6.7 i
  • With no published fix 0 i

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

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
up to 3.0pl1-133 (exclusive) 6
up to 3.0pl1-129 (exclusive) 2
up to 3.0pl1-64 (exclusive) 2

02 Disclosure history

How often vulnerabilities are recorded

  • 2006 2
  • 2017 2
  • 2019 6

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

03 Vulnerabilities

Recorded vulnerabilities for cron

The 5 most severe of 10 vulnerabilities recorded for this package

Search all 10 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Privilege Escalation Vulnerability in Cron Package on Debian and Ubuntu 6.7 medium 3.0pl1-129 09 Jun 2017
Denial of Service in Vixie Cron 5.5 medium 3.0pl1-133 12 Mar 2019
Memory Consumption Denial of Service in Vixie Cron 5.5 medium 3.0pl1-133 12 Mar 2019
Denial of Service Vulnerability in Vixie Cron Package: CVE-2019-9706 5.5 medium 3.0pl1-133 12 Mar 2019
Privilege Escalation in Vixie cron (vixie-cron) 4.1 N/A unrated 3.0pl1-64 25 May 2006

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 cron

Is cron safe to use?

Vulert records 10 vulnerabilities for cron in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 10 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.

How many vulnerabilities does cron have?

10 vulnerabilities are recorded for cron in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 10 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 cron vulnerabilities disclosed?

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

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