VulnerabilityPublished 10 Nov 2025Updated 19 Nov 2025

CVE-2025-40778: bind9.18 security update

Affects bind9.18Source GCVE Database

Compare

Mentioned vulnerabilities

Authoritative record:CVE-2025-40778· High 8.6

Not known to be exploited · CVSS 8.6 High : upgrade to 32:9.18.29-4.el9_6.2 soon.

Data as of 13 Nov 2026, 18:29 UTC

CVSS 3.1 base score

8.6High

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 32:9.18.29-4.el9_6.2

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Changed
Confidentiality: None
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

almalinux-9

What to do

Upgrade the AlmaLinux to 32:9.18.29-4.el9_6.2.

Patches and advisories

access.redhat.com/errata/RHSA-2025:19950 (opens in a new tab)

Affected software

Product	Affected	Fixed in
AlmaLinux 9bind9.18	Affected <32:9.18.29-4.el9_6.2	Fixed in 32:9.18.29-4.el9_6.2
AlmaLinux 9bind9.18-chroot	Affected <32:9.18.29-4.el9_6.2	Fixed in 32:9.18.29-4.el9_6.2
AlmaLinux 9bind9.18-devel	Affected <32:9.18.29-4.el9_6.2	Fixed in 32:9.18.29-4.el9_6.2
AlmaLinux 9bind9.18-dnssec-utils	Affected <32:9.18.29-4.el9_6.2	Fixed in 32:9.18.29-4.el9_6.2
AlmaLinux 9bind9.18-doc	Affected <32:9.18.29-4.el9_6.2	Fixed in 32:9.18.29-4.el9_6.2
AlmaLinux 9bind9.18-libs	Affected <32:9.18.29-4.el9_6.2	Fixed in 32:9.18.29-4.el9_6.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

BIND (Berkeley Internet Name Domain) is an implementation of the DNS (Domain Name System) protocols. BIND includes a DNS server (named), which resolves host names to IP addresses; a resolver library (routines for applications to use when interfacing with DNS); and tools for verifying that the DNS server is operating properly. Security Fix(es): * bind: Cache poisoning attacks with unsolicited RRs (CVE-2025-40778) * bind: Cache poisoning due to weak PRNG (CVE-2025-40780) * bind: Resource exhaustion via malformed DNSKEY handling (CVE-2025-8677) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

References

Community reviews

Loading reviews…