Vulnerability Database · Debian · Package report

tzdata: vulnerability history, versions and safety

tzdata is a package in the Debian ecosystem. Vulert records 6 vulnerabilities for it across 73 releases, from Oct 2022 to Apr 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
6 vulnerabilities recorded U6
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.

Vulert verdict on tzdata i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 6 vulnerabilities on record across 1 year, 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 6 over 1 year · 0 in the last year i
  • Latest disclosure 18 Apr 2024 i
  • Highest CVSS n/a 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

Every version Vulert holds for tzdata, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
2023b-1 U1 Yes Details →
2023a-1 U1 Yes Details →
2023a-1exp1 U1 Yes Details →
2023c-11 U1 Yes Details →
2023c-10 U1 Yes Details →
2023c-9 U1 Yes Details →
2023c-8 U1 Yes Details →
2023c-7 U1 Yes Details →
2023c-6 U1 Yes Details →
2023c-5 U1 Yes Details →
2023c-5exp1 U1 Yes Details →
2023c-4 U1 Yes Details →
2023c-4exp1 U1 Yes Details →
2023c-3 U1 Yes Details →
2023c-3exp1 U1 Yes Details →
2023c-2 U1 Yes Details →
2023c-2exp1 U1 Yes Details →
2023c-1 U1 Yes Details →
2023d-1 U1 Yes Details →
2023c-1exp1 U1 Yes Details →
2022b-1 U1 Yes Details →
2022a-1 U1 Yes Details →
2022g-7 U1 Yes Details →
2022g-7exp2 U1 Yes Details →
2022g-7exp1 U1 Yes Details →
2022g-6 U1 Yes Details →
2022g-5 U1 Yes Details →
2022g-4 U1 Yes Details →
2022g-3 U1 Yes Details →
2022g-2 U1 Yes Details →
2022c-1 U1 Yes Details →
2022d-1 U1 Yes Details →
2022e-1 U1 Yes Details →
2022f-1 U1 Yes Details →
2022g-1 U1 Yes Details →
2021b-1 U1 Yes Details →
2021a-2 U1 Yes Details →
2021a-1 U1 Yes Details →
2021a-0+deb10u12 U1 Yes Details →
2021a-0+deb10u11 U2 Yes Details →
2021a-0+deb10u10 U3 Yes Details →
2021a-0+deb10u9 U4 Yes Details →
2021a-0+deb10u8 U4 Yes Details →
2021a-0+deb10u7 U5 Yes Details →
2021a-0+deb10u6 U6 Yes Details →
2021a-0+deb10u5 U6 Yes Details →
2021a-0+deb10u4 U6 Yes Details →
2021a-0+deb10u3 U6 Yes Details →
2021a-0+deb10u2 U6 Yes Details →
2021a-0+deb10u1 U6 Yes Details →
2021c-3 U1 Yes Details →
2021c-2 U1 Yes Details →
2021c-1 U1 Yes Details →
2021d-1 U1 Yes Details →
2021e-1 U1 Yes Details →
2020b-1 U6 Yes Details →
2020b-0+deb10u1 U6 Yes Details →
2020a-1 U6 Yes Details →
2020a-0+deb10u1 U6 Yes Details →
2020c-1 U6 Yes Details →
2020d-1 U6 Yes Details →
2020e-1 U6 Yes Details →
2020f-1 U6 Yes Details →
2020d-0+deb10u1 U6 Yes Details →
2020e-0+deb10u1 U6 Yes Details →
2019b-2 U6 Yes Details →
2019b-1 U6 Yes Details →
2019b-0+deb10u1 U6 Yes Details →
2019a-1 U6 Yes Details →
2019c-3 U6 Yes Details →
2019c-2 U6 Yes Details →
2019c-1 U6 Yes Details →
2019c-0+deb10u1 U6 Yes Details →

Newest 73 of 73 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2
  • 2023 3
  • 2024 1

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

03 Vulnerabilities

Recorded vulnerabilities for tzdata

The 5 most severe of 6 vulnerabilities recorded for this package

Search all 6 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
New Timezone Database in tzdata N/A unrated 2021a-0+deb10u7 03 Oct 2022
Vulnerability in tzdata package - New Timezone Database N/A unrated 2021a-0+deb10u8 26 Oct 2022
New Timezone Database Vulnerability in tzdata N/A unrated 2021a-0+deb10u10 24 Mar 2023
Vulnerability in tzdata package - New Timezone Database N/A unrated 2021a-0+deb10u11 02 May 2023
New Timezone Database Vulnerability in tzdata N/A unrated 2021a-0+deb10u12 07 Dec 2023

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 tzdata

Is tzdata safe to use?

Vulert records 6 vulnerabilities for tzdata in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 6 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 tzdata have?

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

0 vulnerabilities were recorded for tzdata in the last 12 months, and the oldest entry in this database dates to 03 Oct 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 tzdata 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 tzdata for upcoming vulnerabilities?

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