VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

isc-kea: vulnerability history, versions and safety

isc-kea is a package in the Debian ecosystem. Vulert records 5 vulnerabilities for it across 19 releases, from Nov -0001 to Aug 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded U5
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 isc-kea vulnerabilities

Vulert verdict on isc-kea i

Updated on 23 Oct 2026

Careful: 2 of the 5 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 5 vulnerabilities on record across 2025 years, none in the last year.

What to do: Plan around the 2 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 5 over 2025 years · 0 in the last year i
  • Latest disclosure 27 Aug 2025 i
  • Highest CVSS 7.5 i
  • With no published fix 2 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 isc-kea, 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 19 of 19 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 0 1
  • 2019 3
  • 2025 1

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

03 Vulnerabilities

Recorded vulnerabilities for isc-kea

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Assertion Failure in isc-kea DHCP Server Due to Malformed Client Requests 7.5 high No fix published 27 Aug 2025
Critical Lease Storage Vulnerability in isc-kea Package N/A unrated 1.7.5-1 16 Oct 2019
Critical Vulnerability in isc-kea: Malformed DUID Causes Server Crash N/A unrated 1.7.5-1 16 Oct 2019
Assertion Failure in isc-kea Package Due to Invalid Hostname Option N/A unrated 1.7.5-1 16 Oct 2019
Critical Vulnerability in isc-kea: Potential Security Risks Identified N/A unrated No fix published 30 Nov -0001

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 isc-kea

Is isc-kea safe to use?

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

How many vulnerabilities does isc-kea have?

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

0 vulnerabilities were recorded for isc-kea in the last 12 months, and the oldest entry in this database dates to 30 Nov -0001. 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 isc-kea 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 isc-kea for upcoming vulnerabilities?

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