CVE-2026-50106 Affecting python3-unbound package, versions <0:1.17.1-1.amzn2023.0.17
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-PYTHON3UNBOUND-21705146
- published25 Oct 2026
- disclosed21 Oct 2026
Introduced: 21 Oct 2026
NewCVE-2026-50106 (opens in a new tab)How to fix?
Upgrade Amazon-Linux:2023 python3-unbound to version 0:1.17.1-1.amzn2023.0.17 or higher.
This issue was patched in ALAS2023-2026-3313.
NVD Description
Note: Versions mentioned in the description apply only to the upstream python3-unbound package and not the python3-unbound package as distributed by Amazon-Linux.
See How to fix? for Amazon-Linux:2023 relevant fixed versions and status.
When NLnet Labs Unbound up to and including version 1.26.1 is configured with both a root trust anchor and an additional 'trust-anchor:' for an island-of-security zone whose parent is provably insecure under the root chain, a malicious actor who can deliver one forged NXDOMAIN response for a name inside the island, with the NSEC/SOA RRSIG 'SignerName' set to the insecure parent, tricks Unbound's validator to use the root trust anchor instead, and consecutively the insecure parent, thus causing that record to be treated as insecure and denying existence for records in the trust island.