VulertSecurity VulertSecurity

Vulnerability Database · Alpine · Package report

krb5: vulnerability history, versions and safety

krb5 is a package in the Alpine ecosystem. Vulert records 10 vulnerabilities for it across 32 releases, from Nov 2017 to Nov 2020. 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 krb5 vulnerabilities

Vulert verdict on krb5 i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 10 vulnerabilities on record across 2 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 2 years · 0 in the last year i
  • Latest disclosure 06 Nov 2020 i
  • Highest CVSS 9.8 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 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

  • 2017 2
  • 2018 6
  • 2020 2

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 krb5

The 5 most severe of 10 vulnerabilities recorded for this package

Search all 10 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Buffer Overflow and Application Crash in MIT Kerberos 5 (CVE-2017-15088) 9.8 critical 1.15.3-r0 23 Nov 2017
Critical Buffer Overflow Vulnerability in krb5 Package 9.8 critical 1.15.3-r0 23 Nov 2017
Vulnerability in MIT Kerberos 5 (krb5) Package 7.5 high 1.15.3-r0 16 Jan 2018
Unbounded Recursion in MIT Kerberos 5 7.5 high 1.17.2-r0 06 Nov 2020
Critical Vulnerability in krb5 Package: Integer Overflow in Database Dump Handling 7.5 high 1.15.3-r0 16 Jan 2018

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 10 vulnerabilities for krb5 in Alpine: 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 krb5 have?

10 vulnerabilities are recorded for krb5 in the Alpine 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 krb5 vulnerabilities disclosed?

0 vulnerabilities were recorded for krb5 in the last 12 months, and the oldest entry in this database dates to 23 Nov 2017. 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.