CVE-2026-44621 Affecting unbound-debugsource package, versions <0:1.17.1-1.amzn2023.0.13
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-AMZN2023-UNBOUNDDEBUGSOURCE-18530798
- published5 Aug 2026
- disclosed22 Jul 2026
Introduced: 22 Jul 2026
NewCVE-2026-44621 (opens in a new tab)How to fix?
Upgrade Amazon-Linux:2023 unbound-debugsource to version 0:1.17.1-1.amzn2023.0.13 or higher.
This issue was patched in ALAS2023-2026-2033.
NVD Description
Note: Versions mentioned in the description apply only to the upstream unbound-debugsource package and not the unbound-debugsource package as distributed by Amazon-Linux.
See How to fix? for Amazon-Linux:2023 relevant fixed versions and status.
With NLnet Labs Unbound up to and including version 1.25.1, applications using libunbound and configured with 'unwanted-reply-threshold', could eventually be abruptly terminated if the threshold is reached and libunbound needs to call 'libworker_alloc_cleanup' since the function is absent from the function call allow list. When an application using libunbound sets 'unwanted-reply-threshold' to any non-zero value and the iterator queries an authoritative that replies with enough wrong-transaction-ID UDP datagrams to cross the threshold, the 'libworker_alloc_cleanup' will eventually be called. Since the function is absent from the function call allow list, this leads to a fatal exit of libunbound and eventual termination of the embedding application.Unbound itself is not affected since its relevant function 'worker_alloc_cleanup' is registed in the allow list and proceeds to perform the documented cache flush.