vciy

Isc bind, reachable assertion: 24 records, one defect family

Isc bind has been reported 24 separate times for the same kind of mistake, CWE-617, between 2019-01-16 and 2026-07-22. A defect family is our own grouping of the CVE corpus: every record naming one product and one weakness class, collected so a repeat is visible as a repeat. No public source publishes this, and what this page counts is how often this one product has gone wrong in this one way.

What this page is, and what it is not

The records are public. This grouping is not, and this one took more than a lookup. Every record here carries CWE-617, which matches exactly. The product name does not: the authorities wrote it 3 different ways, and no text match joins those strings, so a search for any one spelling finds a fraction of what exists and gives no sign the rest is there. Our own embedding, pro@dim2000, read those 4 groups, of 12, 8, 2, 2 records, and found they name one product. That is how 24 records no public source connects came to be on one page, and it is the part you cannot look up. Every spelling stays printed beside its own records, because a judgement you cannot inspect is a judgement you should not cite, and if one of them is a different product this family is wrong and its count is wrong with it.

One record is an incident. 24 filings, between 2019-01-16 and 2026-07-22, all landing on the same weakness class in the same product, is a habit in what gets reported here, and a habit is something you can plan around. This is what we held on 2026-09-20.

A repeat is evidence about where to look. If you are reviewing Isc bind, the records below say which mistake has already been found more than once, which is the cheapest place a reviewer can start. If you are asking the vendor a question, a count under one weakness class is a better question than any single record is.

What this page cannot tell you is decided by what was joined. A product name and a weakness class settled membership, so those two values are the whole of what the page asserts. Records here may sit in the same line of code or in unrelated parts of the product, and we hold no value that separates those cases. A fixed version named in one record closes that record and says nothing about the others. And nothing here describes anyone's systems, because no value in this family connects a product name to an installation.

CVE-2022-3488CVE-2022-3924CVE-2023-4236CVE-2023-5517CVE-2023-5679CVE-2024-4076CVE-2025-13878CVE-2025-40777CVE-2026-10822CVE-2026-12617CVE-2026-13204CVE-2026-3119CVE-2017-3136CVE-2017-3137CVE-2017-3138CVE-2018-5734CVE-2018-5737CVE-2018-5740CVE-2019-6467CVE-2019-6476CVE-2022-0635CVE-2022-0667CVE-2019-6468CVE-2019-6469
This family arrived in 4 groups between 2019-01-16 and 2026-07-22. The largest holds 12 of the 24 records and the next holds 8, so no single announcement accounts for most of it.

The names the authorities used

3 different ways, each written by whoever filed the records under it. They are printed as written rather than tidied, because the tidying is the step that would hide what was merged.

isc bind
isc bind 9
isc bind 9 supported preview edition

These records name more than one weakness class each. All 6 carry CWE-617, which is what this family was grouped on, and one of them also names CWE-1284, improper validation of specified quantity in input. The roster below shows what each record names; both readings are the record's own, filed together by the same authority.

Family membership: computed, pro@dim2000

What pulled them together

These records reached one family from 4 separate groups. A join on the product name alone could not see they were the same, because the authorities wrote the product and its versions differently each time. The grouping was computed by pro@dim2000.

12 recordsCVE-2022-3488, CVE-2022-3924, CVE-2023-4236, CVE-2023-5517, CVE-2023-5679, CVE-2024-4076, CVE-2025-13878, CVE-2025-40777, CVE-2026-10822…
8 recordsCVE-2017-3136, CVE-2017-3137, CVE-2017-3138, CVE-2018-5734, CVE-2018-5737, CVE-2018-5740, CVE-2019-6467, CVE-2019-6476
2 recordsCVE-2022-0635, CVE-2022-0667
2 recordsCVE-2019-6468, CVE-2019-6469

What the records offer

No record in this family publishes a fixed version in held sources.

The earliest was published 2019-01-16 and the latest 2026-07-22. That span is how long this product kept producing this weakness, not how long any one record took to fix.

What this page does not cover

This is a family of records that read alike. It is not a shared vulnerability, not an inventory, and not a statement that one fix closes the rest. Each record's own state, its own dates and its own receipts are on its own page.

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Everything this vendor has, including records outside this family:

CVE-2017-3136An error handling synthesized records could cause an assertion failure when using DNS64 with "break-dnssec yes;"Servers are at risk if they are configured to…
CVE-2017-3137A response packet can cause a resolver to terminate when processing an answer containing a CNAME or DNAME
CVE-2017-3138named exits with a REQUIRE assertion failure if it receives a null command string on its control channelThe BIND control channel is not configured by…
CVE-2018-5734A malformed request can trigger an assertion failure in badcache.cServers running the affected versions…
CVE-2018-5737BIND 9.12's serve-stale implementation can cause an assertion failure in rbtdb.c or other undesirable behavior, even if…Servers running a vulnerable version of BIND…
CVE-2018-5740A flaw in the "deny-answer-aliases" feature can cause an assertion failure in namedAccidental or deliberate triggering of this…
CVE-2019-6467An error in the nxdomain redirect feature can cause BIND to exit with an INSIST assertion failure in query.c
CVE-2019-6468BIND Supported Preview Edition can exit with an assertion failure if nxdomain-redirect is usedIf nxdomain-redirect is enabled (via…
CVE-2019-6469BIND Supported Preview Edition can exit with an assertion failure if ECS is in useAn attacker who is able to cause a server to…
CVE-2019-6476An error in QNAME minimization code can cause BIND to exit with an assertion failure
CVE-2022-0635no title heldWe refactored the RFC 8198 Aggressive Use of…
CVE-2022-0667Assertion failure on delayed DS lookupIn BIND 9.18.0 the recursive client code was…
CVE-2022-3488named may terminate unexpectedly when processing ECS options in repeated responses to iterative queries
CVE-2022-3924named configured to answer from stale cache may terminate unexpectedly at recursive-clients soft quota
CVE-2023-4236named may terminate unexpectedly under high DNS-over-TLS query load
CVE-2023-5517Querying RFC 1918 reverse zones may cause an assertion failure when "nxdomain-redirect" is enabled
CVE-2023-5679Enabling both DNS64 and serve-stale may cause an assertion failure during recursive resolution
CVE-2024-4076Assertion failure when serving both stale cache data and authoritative zone content
CVE-2025-13878Malformed BRID/HHIT records can cause named to terminate unexpectedlyCWE-617 Reachable Assertion
CVE-2025-40777A possible assertion failure when 'stale-answer-client-timeout' is set to '0'CWE-617 Reachable Assertion
CVE-2026-10822Key Record using PRIVATEDNS algorithm may lead to unexpected exitCWE-617 Reachable Assertion
CVE-2026-12617Record ordering based unexpected exit with CNAME or DNAMECWE-617 Reachable Assertion
CVE-2026-13204Unexpected exit in certain situations with NSEC and NSEC3 both presentCWE-617 Reachable Assertion
CVE-2026-3119Authenticated query containing a TKEY record may cause named to terminate unexpectedlyCWE-617 Reachable Assertion

24 records, read from the index as it stood on 20 Sep 2026. Every row opens the record it names, and every value on that record opens its own receipt.

Everything on this page is free. Public data. Withholding it protects nothing.