VulertSecurity VulertSecurity

Vulnerability Database · AlmaLinux · Package report

bind9.16: vulnerability history, versions and safety

bind9.16 is a package in the AlmaLinux ecosystem. Vulert records 14 vulnerabilities for it across 14 affected ranges, from May 2022 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
14 vulnerabilities recorded U14
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
5 in the last 12 months

Most recent disclosure 08 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all bind9.16 vulnerabilities

Vulert verdict on bind9.16 i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 14 vulnerabilities on record across 4 years, 5 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 14 over 4 years · 5 in the last year i
  • Latest disclosure 08 Oct 2026 i
  • Highest CVSS n/a 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

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
up to 32:9.16.23-0.22.el8_10.16 (exclusive) 1
up to 32:9.16.23-0.22.el8_10.12 (exclusive) 1
up to 32:9.16.23-0.22.el8_10.6 (exclusive) 1
up to 32:9.16.23-0.22.el8_10.5 (exclusive) 1
up to 32:9.16.23-0.22.el8_10.4 (exclusive) 1
up to 32:9.16.23-0.22.el8_10.2 (exclusive) 1
up to 32:9.16.23-0.22.el8_10 (exclusive) 1
up to 32:9.16.23-0.16.el8_9.2.alma.1 (exclusive) 1
up to 32:9.16.23-0.14.el8_8.2.alma.1 (exclusive) 1
up to 32:9.16.23-0.14.el8_8.1.alma (exclusive) 1
up to 32:9.16.23-0.14.el8 (exclusive) 1
up to 32:9.16.23-0.9.el8.1 (exclusive) 1
up to 32:9.16.23-0.7.el8_6.1 (exclusive) 1
up to 32:9.16.23-0.7.el8 (exclusive) 1

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 3
  • 2023 3
  • 2024 2
  • 2025 2
  • 2026 4

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

03 Vulnerabilities

Recorded vulnerabilities for bind9.16

The 5 most severe of 14 vulnerabilities recorded for this package

Search all 14 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Security Update for BIND 9.16: Memory Exhaustion and Denial of Service Vulnerabilities N/A unrated 32:9.16.23-0.22.el8_10.6 04 Jun 2026
Critical CPU Exhaustion Vulnerability in bind9.16 Package N/A unrated 32:9.16.23-0.22.el8_10.2 19 Feb 2025
Critical Security Update for BIND 9.16: Cache Poisoning Vulnerabilities N/A unrated 32:9.16.23-0.22.el8_10.4 05 Nov 2025
Critical Security Update for BIND 9.16: Denial of Service Vulnerability N/A unrated 32:9.16.23-0.22.el8_10.5 14 Apr 2026
Important: bind9.16 security update N/A unrated 32:9.16.23-0.22.el8_10 14 Aug 2024

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 bind9.16

Is bind9.16 safe to use?

Vulert records 14 vulnerabilities for bind9.16 in AlmaLinux: 0 critical, 0 high, 0 medium and 0 low, plus 14 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 bind9.16 have?

14 vulnerabilities are recorded for bind9.16 in the AlmaLinux ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 14 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 bind9.16 vulnerabilities disclosed?

5 vulnerabilities were recorded for bind9.16 in the last 12 months, and the oldest entry in this database dates to 10 May 2022. 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 bind9.16 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 bind9.16 for upcoming vulnerabilities?

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