Skip to main content
Mallory
HighVulnerability

CVE-2025-13878: DoS in ISC BIND 9 named via malformed BRID/HHIT records

Published Jan 21, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.5High · v3.1
EPSS9.4%96th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Internet Systems Consortium
IdentifiersCVE-2025-13878CWE-617 · Reachable Assertion

CVE-2025-13878 is a denial-of-service vulnerability in ISC BIND 9 affecting the named daemon’s handling of BRID and HHIT DNS resource records. Malformed BRID or HHIT records with undersized or otherwise invalid RDATA can reach assertion conditions during record processing and re-encoding, causing named to terminate unexpectedly. Reported crash paths involve dns_rdata_towire()-related assertions in the BRID and HHIT record handling code. The issue affects BIND 9 versions 9.18.40 through 9.18.43, 9.20.13 through 9.20.17, 9.21.12 through 9.21.16, 9.18.40-S1 through 9.18.43-S1, and 9.20.13-S1 through 9.20.17-S1.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation causes the named process to abort, producing a denial-of-service condition. On recursive resolvers or forwarders, a malicious upstream response containing a malformed BRID or HHIT record can immediately terminate the service and deny DNS resolution to clients until the daemon is restarted. The documented impact is availability loss rather than confidentiality or integrity compromise.

Mitigation

If you can’t patch tonight, do this now.

No vendor workaround is available for affected resolvers according to the available advisory information. The effective mitigation is patching. Until upgrades can be completed, reduce exposure where operationally feasible by limiting recursion and forwarding to trusted clients and trusted upstream infrastructure, restricting network access to DNS services with ACLs or filtering, and monitoring for unexpected named crashes or restart loops.

Remediation

Patch, then assume compromise.

Upgrade to a fixed BIND 9 release for the deployed branch. Fixed versions identified in the available information are 9.18.44, 9.20.18, and 9.21.17, with corresponding fixed Subscription Edition releases 9.18.44-S1 and 9.20.18-S1. Where distribution-packaged BIND is used, apply the vendor-provided security update that incorporates the upstream fix.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Internet Systems ConsortiumBindapplication
FAQ

Frequently asked questions

Is CVE-2025-13878 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2025-13878 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-13878?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2025-13878.
Is there a patch for CVE-2025-13878?
Upgrade to a fixed BIND 9 release for the deployed branch. Fixed versions identified in the available information are 9.18.44, 9.20.18, and 9.21.17, with corresponding fixed Subscription Edition releases 9.18.44-S1 and 9.20.18-S1.
What products are affected by CVE-2025-13878?
Internet Systems Consortium Bind.
How severe is CVE-2025-13878?
CVE-2025-13878 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 9.4% (96th percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity32Community discussion across Reddit, Mastodon, and other social sources.