CVE-2026-50046 (GCVE-0-2026-50046)

Vulnerability from cvelistv5 – Published: 2026-07-22 13:08 – Updated: 2026-07-22 18:57
VLAI
Title
Possible heap use-after-free in an error path when a DoT forwarded query is jostled out
Summary
In NLnet Labs Unbound 1.15.0 up to and including 1.25.1, the TLS server name used for DNS-over-TLS (DoT) forwarded queries is tied to a struct's ('serviced_query') lifetime but also referenced by another struct ('waiting_tcp'). When the owning struct is jostled out of the mesh while the DoT TCP stream is still handshaking it frees the storage behind the referenced string and if the TLS stream then errors out, it dereferences the freed pointer. The dereference is read-only and the practical impact is a daemon crash resulting in denial of service. A malicious actor that knows a DoT forwarding/stub Unbound's configuration could exploit the vulnerability by quering records in the appropriate zone while keeping Unbound uder pressure so that the jostle logic kicks in. If answers for the vulnerable zone are slow, the likelihood of jostling such queries is higher, although the timing of the jostle needs to be precise. Requirements for a vulnerable Unbound is the existence of a stub/forward zone configured for DoT together with a configured '#authname' suffix on the server identification. The connectivity to the server needs to exhibit a transient failure at the correct time in order to kick off the vulnerable error path.
SSVC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-07-22 18:57 UTC
CWE
Assigner
CNA scorecard B 81/100 over 66 records in the last 180 days details
References
Impacted products
Vendor Product Version CPE status
NLnet Labs Unbound Affected: 1.15.0 , < 1.25.2 (semver)
guessed Create a notification for this product.
Date Public
2026-07-22 00:00
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-50046",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-07-22T18:57:24.481710Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-07-22T18:57:33.147Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Unbound",
          "vendor": "NLnet Labs",
          "versions": [
            {
              "lessThan": "1.25.2",
              "status": "affected",
              "version": "1.15.0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Qifan Zhang (Palo Alto Networks)"
        }
      ],
      "datePublic": "2026-07-22T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "In NLnet Labs Unbound 1.15.0 up to and including 1.25.1, the TLS server name used for DNS-over-TLS (DoT) forwarded queries is tied to a struct\u0027s (\u0027serviced_query\u0027) lifetime but also referenced by another struct (\u0027waiting_tcp\u0027). When the owning struct is jostled out of the mesh while the DoT TCP stream is still handshaking it frees the storage behind the referenced string and if the TLS stream then errors out, it dereferences the freed pointer. The dereference is read-only and the practical impact is a daemon crash resulting in denial of service. A malicious actor that knows a DoT forwarding/stub Unbound\u0027s configuration could exploit the vulnerability by quering records in the appropriate zone while keeping Unbound uder pressure so that the jostle logic kicks in. If answers for the vulnerable zone are slow, the likelihood of jostling such queries is higher, although the timing of the jostle needs to be precise. Requirements for a vulnerable Unbound is the existence of a stub/forward zone configured for DoT together with a configured \u0027#authname\u0027 suffix on the server identification. The connectivity to the server needs to exhibit a transient failure at the correct time in order to kick off the vulnerable error path."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 5.9,
            "baseSeverity": "MEDIUM",
            "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H",
            "version": "3.1"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-416",
              "description": "CWE-416: Use After Free",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-07-22T13:08:08.710Z",
        "orgId": "206fc3a0-e175-490b-9eaa-a5738056c9f6",
        "shortName": "NLnet Labs"
      },
      "references": [
        {
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://www.nlnetlabs.nl/downloads/unbound/CVE-2026-50046.txt"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "value": "This issue is fixed starting with version 1.25.2"
        }
      ],
      "timeline": [
        {
          "lang": "en",
          "time": "2026-05-04T00:00:00.000Z",
          "value": "Issue reported by Qifan Zhang"
        },
        {
          "lang": "en",
          "time": "2026-05-29T00:00:00.000Z",
          "value": "NLnet Labs shares patch"
        },
        {
          "lang": "en",
          "time": "2026-05-30T00:00:00.000Z",
          "value": "Qifan Zhang verifies patch"
        },
        {
          "lang": "en",
          "time": "2026-07-22T00:00:00.000Z",
          "value": "Fixes released with version 1.25.2"
        }
      ],
      "title": "Possible heap use-after-free in an error path when a DoT forwarded query is jostled out",
      "x_generator": {
        "engine": "cvelib 1.8.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "206fc3a0-e175-490b-9eaa-a5738056c9f6",
    "assignerShortName": "NLnet Labs",
    "cveId": "CVE-2026-50046",
    "datePublished": "2026-07-22T13:08:08.710Z",
    "dateReserved": "2026-06-22T12:27:22.824Z",
    "dateUpdated": "2026-07-22T18:57:33.147Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-50046",
      "date": "2026-11-21",
      "epss": "0.00237",
      "percentile": "0.14866"
    },
    "microsoft_vex": {
      "current_release_date": "2026-07-23T14:44:26.000Z",
      "cve": "CVE-2026-50046",
      "id": "msrc_CVE-2026-50046",
      "initial_release_date": "2026-07-23T01:04:51.000Z",
      "product_status:fixed": "1",
      "product_status:known_affected": "1",
      "source": "Microsoft CSAF VEX",
      "status": "final",
      "title": "Possible heap use-after-free in an error path when a DoT forwarded query is jostled out",
      "url": "https://msrc.microsoft.com/csaf/vex/2026/msrc_cve-2026-50046.json",
      "version": "2"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "defaultStatus": "unaffected",
                "product": "Unbound",
                "vendor": "NLnet Labs",
                "versions": [
                  {
                    "lessThan": "1.25.2",
                    "status": "affected",
                    "version": "1.15.0",
                    "versionType": "semver"
                  }
                ]
              }
            ],
            "source": "sep@nlnetlabs.nl"
          }
        ],
        "configurations": [
          {
            "nodes": [
              {
                "cpeMatch": [
                  {
                    "criteria": "cpe:2.3:a:nlnetlabs:unbound:*:*:*:*:*:*:*:*",
                    "matchCriteriaId": "16043273-E324-4533-93D1-27C32803A2F9",
                    "versionEndExcluding": "1.25.2",
                    "versionStartIncluding": "1.15.0",
                    "vulnerable": true
                  }
                ],
                "negate": false,
                "operator": "OR"
              }
            ]
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "In NLnet Labs Unbound 1.15.0 up to and including 1.25.1, the TLS server name used for DNS-over-TLS (DoT) forwarded queries is tied to a struct\u0027s (\u0027serviced_query\u0027) lifetime but also referenced by another struct (\u0027waiting_tcp\u0027). When the owning struct is jostled out of the mesh while the DoT TCP stream is still handshaking it frees the storage behind the referenced string and if the TLS stream then errors out, it dereferences the freed pointer. The dereference is read-only and the practical impact is a daemon crash resulting in denial of service. A malicious actor that knows a DoT forwarding/stub Unbound\u0027s configuration could exploit the vulnerability by quering records in the appropriate zone while keeping Unbound uder pressure so that the jostle logic kicks in. If answers for the vulnerable zone are slow, the likelihood of jostling such queries is higher, although the timing of the jostle needs to be precise. Requirements for a vulnerable Unbound is the existence of a stub/forward zone configured for DoT together with a configured \u0027#authname\u0027 suffix on the server identification. The connectivity to the server needs to exhibit a transient failure at the correct time in order to kick off the vulnerable error path."
          },
          {
            "lang": "es",
            "value": "En NLnet Labs Unbound 1.15.0 hasta la versi\u00f3n 1.25.1 inclusive, el nombre del servidor TLS utilizado para consultas reenviadas de DNS-over-TLS (DoT) est\u00e1 vinculado al ciclo de vida de una estructura (\u2019serviced_query\u2019) pero tambi\u00e9n referenciado por otra estructura (\u2019waiting_tcp\u2019). Cuando la estructura propietaria es desalojada de la malla mientras el flujo TCP de DoT a\u00fan est\u00e1 realizando el \u2019handshake\u2019, libera el almacenamiento detr\u00e1s de la cadena referenciada y, si el flujo TLS luego falla, desreferencia el puntero liberado. La desreferencia es de solo lectura y el impacto pr\u00e1ctico es un fallo del demonio que resulta en denegaci\u00f3n de servicio. Un actor malicioso que conoce la configuraci\u00f3n de un Unbound de reenv\u00edo/stub de DoT podr\u00eda explotar la vulnerabilidad consultando registros en la zona apropiada mientras mantiene a Unbound bajo presi\u00f3n para que la l\u00f3gica de desalojo se active. Si las respuestas para la zona vulnerable son lentas, la probabilidad de desalojar dichas consultas es mayor, aunque el momento del desalojo debe ser preciso. Los requisitos para un Unbound vulnerable son la existencia de una zona stub/forward configurada para DoT junto con un sufijo \u2019#authname\u2019 configurado en la identificaci\u00f3n del servidor. La conectividad al servidor necesita exhibir un fallo transitorio en el momento correcto para activar la ruta de error vulnerable."
          }
        ],
        "id": "CVE-2026-50046",
        "lastModified": "2026-10-24T13:10:00.147",
        "metrics": {
          "cvssMetricV31": [
            {
              "cvssData": {
                "attackComplexity": "HIGH",
                "attackVector": "NETWORK",
                "availabilityImpact": "HIGH",
                "baseScore": 5.9,
                "baseSeverity": "MEDIUM",
                "confidentialityImpact": "NONE",
                "integrityImpact": "NONE",
                "privilegesRequired": "NONE",
                "scope": "UNCHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H",
                "version": "3.1"
              },
              "exploitabilityScore": 2.2,
              "impactScore": 3.6,
              "source": "sep@nlnetlabs.nl",
              "type": "Secondary"
            }
          ],
          "ssvcV203": [
            {
              "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "ssvcData": {
                "id": "CVE-2026-50046",
                "options": [
                  {
                    "exploitation": "none"
                  },
                  {
                    "automatable": "no"
                  },
                  {
                    "technicalImpact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-07-22T18:57:24.481710Z",
                "version": "2.0.3"
              }
            }
          ]
        },
        "published": "2026-07-22T14:17:20.117",
        "references": [
          {
            "source": "sep@nlnetlabs.nl",
            "tags": [
              "Vendor Advisory"
            ],
            "url": "https://www.nlnetlabs.nl/downloads/unbound/CVE-2026-50046.txt"
          }
        ],
        "sourceIdentifier": "sep@nlnetlabs.nl",
        "vulnStatus": "Analyzed",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-416"
              }
            ],
            "source": "sep@nlnetlabs.nl",
            "type": "Secondary"
          }
        ]
      }
    },
    "redhat_vex": {
      "aggregate_severity": "Low",
      "current_release_date": "2026-11-12T17:45:28+00:00",
      "cve": "CVE-2026-50046",
      "id": "CVE-2026-50046",
      "initial_release_date": "2026-07-22T13:08:08.710000+00:00",
      "product_status:fixed": "197",
      "product_status:known_affected": "8",
      "product_status:known_not_affected": "10",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "unbound: Unbound: Denial of Service due to freed pointer dereference in DNS-over-TLS handling",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-50046.json",
      "version": "3"
    },
    "suse_vex": {
      "aggregate_severity": "moderate",
      "current_release_date": "2026-09-10T17:01:37Z",
      "cve": "CVE-2026-50046",
      "id": "CVE-2026-50046",
      "initial_release_date": "2026-07-26T23:31:56Z",
      "product_status:known_affected": "56",
      "product_status:recommended": "86",
      "source": "SUSE CSAF VEX",
      "status": "interim",
      "title": "SUSE CVE CVE-2026-50046",
      "url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2026-50046.json",
      "version": "11"
    },
    "vulnrichment": {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-50046",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "no"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-07-22T18:57:24.481710Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-07-22T18:57:28.535Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "defaultStatus": "unaffected",
              "product": "Unbound",
              "vendor": "NLnet Labs",
              "versions": [
                {
                  "lessThan": "1.25.2",
                  "status": "affected",
                  "version": "1.15.0",
                  "versionType": "semver"
                }
              ]
            }
          ],
          "credits": [
            {
              "lang": "en",
              "type": "finder",
              "value": "Qifan Zhang (Palo Alto Networks)"
            }
          ],
          "datePublic": "2026-07-22T00:00:00.000Z",
          "descriptions": [
            {
              "lang": "en",
              "value": "In NLnet Labs Unbound 1.15.0 up to and including 1.25.1, the TLS server name used for DNS-over-TLS (DoT) forwarded queries is tied to a struct\u0027s (\u0027serviced_query\u0027) lifetime but also referenced by another struct (\u0027waiting_tcp\u0027). When the owning struct is jostled out of the mesh while the DoT TCP stream is still handshaking it frees the storage behind the referenced string and if the TLS stream then errors out, it dereferences the freed pointer. The dereference is read-only and the practical impact is a daemon crash resulting in denial of service. A malicious actor that knows a DoT forwarding/stub Unbound\u0027s configuration could exploit the vulnerability by quering records in the appropriate zone while keeping Unbound uder pressure so that the jostle logic kicks in. If answers for the vulnerable zone are slow, the likelihood of jostling such queries is higher, although the timing of the jostle needs to be precise. Requirements for a vulnerable Unbound is the existence of a stub/forward zone configured for DoT together with a configured \u0027#authname\u0027 suffix on the server identification. The connectivity to the server needs to exhibit a transient failure at the correct time in order to kick off the vulnerable error path."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "baseScore": 5.9,
                "baseSeverity": "MEDIUM",
                "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H",
                "version": "3.1"
              },
              "format": "CVSS",
              "scenarios": [
                {
                  "lang": "en",
                  "value": "GENERAL"
                }
              ]
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-416",
                  "description": "CWE-416: Use After Free",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-07-22T13:08:08.710Z",
            "orgId": "206fc3a0-e175-490b-9eaa-a5738056c9f6",
            "shortName": "NLnet Labs"
          },
          "references": [
            {
              "tags": [
                "vendor-advisory"
              ],
              "url": "https://www.nlnetlabs.nl/downloads/unbound/CVE-2026-50046.txt"
            }
          ],
          "solutions": [
            {
              "lang": "en",
              "value": "This issue is fixed starting with version 1.25.2"
            }
          ],
          "timeline": [
            {
              "lang": "en",
              "time": "2026-05-04T00:00:00.000Z",
              "value": "Issue reported by Qifan Zhang"
            },
            {
              "lang": "en",
              "time": "2026-05-29T00:00:00.000Z",
              "value": "NLnet Labs shares patch"
            },
            {
              "lang": "en",
              "time": "2026-05-30T00:00:00.000Z",
              "value": "Qifan Zhang verifies patch"
            },
            {
              "lang": "en",
              "time": "2026-07-22T00:00:00.000Z",
              "value": "Fixes released with version 1.25.2"
            }
          ],
          "title": "Possible heap use-after-free in an error path when a DoT forwarded query is jostled out",
          "x_generator": {
            "engine": "cvelib 1.8.0"
          }
        }
      },
      "cveMetadata": {
        "assignerOrgId": "206fc3a0-e175-490b-9eaa-a5738056c9f6",
        "assignerShortName": "NLnet Labs",
        "cveId": "CVE-2026-50046",
        "datePublished": "2026-07-22T13:08:08.710Z",
        "dateReserved": "2026-06-22T12:27:22.824Z",
        "dateUpdated": "2026-07-22T18:57:33.147Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}


Solutions

CNA · NLnet Labs
This issue is fixed starting with version 1.25.2

Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.