VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

krb5: vulnerability history, versions and safety

krb5 is a package in the Debian ecosystem. Vulert records 221 vulnerabilities for it across 32 releases, from Feb 2003 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
221 vulnerabilities recorded U221
i
8 with no fix published

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

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

Most recent disclosure 11 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all krb5 vulnerabilities

Vulert verdict on krb5 i

Updated on 23 Oct 2026

Careful: 8 of the 221 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 221 vulnerabilities on record across 23 years, 3 in the last year.

What to do: Plan around the 8 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 221 over 23 years · 3 in the last year i
  • Latest disclosure 11 Jun 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 8 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 krb5, 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.

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2003 12
  • 2004 12
  • 2005 12
  • 2006 6
  • 2007 28
  • 2008 8
  • 2009 10
  • 2010 20
  • 2011 20
  • 2012 8
  • 2013 12
  • 2014 16
  • 2015 20
  • 2016 5
  • 2017 5
  • 2018 7
  • 2020 1
  • 2021 2
  • 2022 1
  • 2023 1
  • 2024 7
  • 2025 5
  • 2026 3

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

03 Vulnerabilities

Recorded vulnerabilities for krb5

The 5 most severe of 221 vulnerabilities recorded for this package

Search all 221 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2008-0062: Denial of Service and Arbitrary Code Execution in MIT Kerberos 5 9.8 critical 1.6.dfsg.3~beta1-4 19 Mar 2008
Critical Double Free Vulnerability in krb5 Package: Remote Code Execution Risk 9.8 critical 1.3.4-3 20 Oct 2004
Double Free Vulnerability in MIT Kerberos 5 9.8 critical 1.15.2-1 13 Sep 2017
Double Free Vulnerability in MIT Kerberos 5 (krb5) 9.8 critical 1.3.6-4 18 Jul 2005
Uninitialized stack values in MIT Kerberos 5 (krb5kdc) 7.5 high 1.6.dfsg.3~beta1-4 19 Mar 2008

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 krb5

Is krb5 safe to use?

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

How many vulnerabilities does krb5 have?

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

3 vulnerabilities were recorded for krb5 in the last 12 months, and the oldest entry in this database dates to 19 Feb 2003. 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 krb5 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 krb5 for upcoming vulnerabilities?

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