VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

pdns: vulnerability history, versions and safety

pdns is a package in the Debian ecosystem. Vulert records 76 vulnerabilities for it across 43 releases, from May 2005 to May 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
76 vulnerabilities recorded U76
i
10 with no fix published

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

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

Most recent disclosure 20 May 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all pdns vulnerabilities

Vulert verdict on pdns i

Updated on 23 Oct 2026

Careful: 10 of the 76 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 76 vulnerabilities on record across 21 years, 9 in the last year.

What to do: Plan around the 10 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 76 over 21 years · 9 in the last year i
  • Latest disclosure 20 May 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 10 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 pdns, 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 43 of 43 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2005 8
  • 2006 2
  • 2008 4
  • 2012 2
  • 2015 6
  • 2016 6
  • 2018 18
  • 2019 8
  • 2020 10
  • 2022 1
  • 2025 2
  • 2026 9

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

03 Vulnerabilities

Recorded vulnerabilities for pdns

The 5 most severe of 76 vulnerabilities recorded for this package

Search all 76 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Double-Free Vulnerability in PowerDNS Authoritative 9.8 critical 4.4.0-1 02 Oct 2020
PowerDNS Authoritative Server Denial of Service and Information Disclosure Vulnerability 8.8 high 4.1.6-2 21 Mar 2019
Race Condition Vulnerability in PowerDNS Authoritative 8.1 high 4.4.0-1 02 Oct 2020
Buffer Overflow Vulnerability in PowerDNS (CVE-2018-1046) 7.8 high 4.1.2-1 16 Jul 2018
Denial of Service Vulnerability in PowerDNS Authoritative 7.5 high 4.4.0-1 02 Oct 2020

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 pdns

Is pdns safe to use?

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

How many vulnerabilities does pdns have?

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

9 vulnerabilities were recorded for pdns in the last 12 months, and the oldest entry in this database dates to 02 May 2005. 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 pdns 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 pdns for upcoming vulnerabilities?

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