VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

unbound: vulnerability history, versions and safety

unbound is a package in the Debian ecosystem. Vulert records 96 vulnerabilities for it across 47 releases, from Oct 2009 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
96 vulnerabilities recorded U96
i
36 with no fix published

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

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

Most recent disclosure 22 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all unbound vulnerabilities

Vulert verdict on unbound i

Updated on 22 Oct 2026

Careful: 36 of the 96 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 96 vulnerabilities on record across 16 years, 37 in the last year.

What to do: Plan around the 36 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 96 over 16 years · 37 in the last year i
  • Latest disclosure 22 Jul 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 36 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 unbound, 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 47 of 47 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2009 2
  • 2010 2
  • 2011 8
  • 2014 2
  • 2018 2
  • 2019 2
  • 2020 2
  • 2021 24
  • 2022 3
  • 2024 9
  • 2025 5
  • 2026 35

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

03 Vulnerabilities

Recorded vulnerabilities for unbound

The 5 most severe of 96 vulnerabilities recorded for this package

Search all 96 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Integer Overflow in Unbound (CVE-2019-25034) 9.8 critical 1.9.6-1 27 Apr 2021
Integer Overflow in Unbound dnscrypt.c 9.8 critical 1.9.6-1 27 Apr 2021
Out-of-Bounds Write Vulnerability in Unbound 9.8 critical 1.9.6-1 27 Apr 2021
Integer Overflow Vulnerability in Unbound 9.8 critical 1.9.6-1 27 Apr 2021
Integer Overflow Vulnerability in Unbound 9.8 critical 1.9.6-1 27 Apr 2021

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 unbound

Is unbound safe to use?

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

How many vulnerabilities does unbound have?

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

37 vulnerabilities were recorded for unbound in the last 12 months, and the oldest entry in this database dates to 13 Oct 2009. 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 unbound 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 unbound for upcoming vulnerabilities?

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