CVE-2026-123585 is a vulnerability in the hickory-resolver component of Hickory DNS versions 0.25.0 through before 0.26.2. The resolver follows irrelevant CNAME records during recursive DNS queries, causing unnecessary additional queries. This behavior can be exploited by attackers controlling DNS responses to trigger excessive resolver queries and increase query amplification. The issue is fixed in version 0.26.2.
This security update for BIND addresses multiple vulnerabilities including unauthenticated application of IXFR deltas before TSIG verification, use-after-free crashes in the recursive resolver, resource exhaustion via excessive DNSSEC cryptographic material, acceptance of out-of-zone NSEC as wildcard-nonexistence proof, message parser amplification issues, insecure NSEC3 referral proofs, and out-of-zone database nodes becoming authoritative zone cuts.
A stack-based buffer overflow vulnerability exists in the lwIP DNS resolver component of Espressif's ESP-IDF framework. The flaw occurs when the DNS resolver copies multiple cached IP addresses into a single-element buffer without bounds checking, leading to potential stack memory corruption. This can cause device reboots or, without stack protection, allow an attacker to overwrite stack variables and potentially redirect control flow. The vulnerability affects multiple ESP-IDF versions from 5.2.3 up to but not including fixed versions 5.3.7, 5.4.5, 5.5.6, and 6.0.3. The issue is rated high severity with a CVSS score of 7.4. Fixed versions are available for most affected branches except the end-of-life 5.2 line.
Multiple security vulnerabilities affect NLnet Labs Unbound up to and including version 1.26.1. These include a cache-level side-channel vulnerability that can leak upstream source port information under specific configurations, DNSSEC validation bypasses that can cause trust islands to be treated as insecure, and a performance degradation issue via chained compression pointers. These flaws can lead to cache poisoning, denial of DNS record existence, and degraded resolver performance. A fix is available in version 1.17.1-25.oe2403sp1.
This Red Hat Security Advisory addresses multiple vulnerabilities in the Berkeley Internet Name Domain (BIND) 9 DNS software, including memory exhaustion, denial of service, DNSSEC validation bypass, cache poisoning, and arbitrary code execution. The advisory covers a range of CVEs affecting BIND 9 server and resolver components, with impacts such as denial of service via crafted DNS messages, resource exhaustion, and potential remote code execution. The update also includes a new root trust anchor key for DNSSEC. The advisory rates the security impact as Important and provides fixes for all listed issues.
CVE-2026-83813 is a vulnerability in the Twisted framework's DNS client UDP transport (twisted.names.dns.DNSDatagramProtocol) where DNS responses are accepted based only on matching transaction IDs without validating the source address. This allows an off-path attacker who can send UDP packets to the resolver's port to spoof DNS responses. The standard Twisted DNS client mitigates this by using per-query random source ports, increasing entropy, but the missing source address validation remains a weakness, especially for code using DNSDatagramProtocol directly. The CVSS score is low due to the attack complexity and limited impact.
CVE-2026-118275 is a resource consumption vulnerability in the a2ui-project a2ui component, specifically affecting versions 0.10.0 through 0.10.6. The flaw exists in the DataContext.resolveSignal function within the Resolver component, allowing remote attackers to cause excessive resource usage. Public exploit code is available, and a patch has been identified to address the issue.
CVE-2026-118271 is a medium-severity vulnerability in a2ui-project's a2ui component versions 0.10.0 through 0.10.6. It involves resource consumption caused by manipulation of an unknown function in the data-context Resolver within the file renderers/web_core/src/v0_9/rendering/data-context.ts. The vulnerability can be exploited remotely without user interaction and requires low privileges. Public exploit code has been disclosed. A patch identified by commit eb314e14fabd29cfb4a74e1202afc4fe2081efa2 is available to address this issue.
A path traversal vulnerability exists in the View Name Resolver component of halo-dev halo up to version 2.27.0-beta.1. The flaw is in the function run.halo.app.theme.DefaultViewNameResolver.resolveViewNameOrDefault, where manipulation of the template argument can lead to unauthorized file path access. The vulnerability can be exploited remotely. Public exploit code is available. The vendor was contacted but did not respond or provide a fix.
A denial of service vulnerability exists in BIND 9 due to crafted DNSSEC responses. This issue affects the Berkeley Internet Name Domain (BIND) DNS server and resolver components. Red Hat has issued a security update to address this vulnerability in Red Hat Enterprise Linux 9.8 and related products. The vulnerability is rated as moderate in severity by Red Hat. No public exploit code or in-the-wild exploitation has been reported.
A flaw in Node.js TLS hostname verification can cause a server certificate to be validated against a different IP address than the one the client connected to, when the host is a non-canonical IPv4 literal with a leading zero, such as `0127.0.0.1`.
`tls.checkServerIdentity()` normalizes the host following the WHATWG URL rules, which read a leading-zero octet as octal (`0127.0.0.1` becomes `87.0.0.1`), while the connection is made through the operating system resolver, which on some platforms such as macOS reads it as decimal (`127.0.0.1`). A server at the connected address can then be authenticated with a certificate issued for another IP address.
This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.
A flaw has been found in pig-mesh pig up to 4.1.0. This impacts the function orderItem.getColumn of the file pig-common/pig-common-data/src/main/java/com/pig4cloud/pig/common/data/resolver/SqlFilterArgumentResolver.java. Executing a manipulation of the argument ascs/descs can lead to sql injection. The attack may be launched remotely. The exploit has been published and may be used. Upgrading to version 4.1.1 will fix this issue. This patch is called 9b6311161e346d7626c81d993044072fed2dca07. It is suggested to upgrade the affected component. The vendor was contacted early about this disclosure.
hydra-ray-launcher versions 1.1.0.dev1 up to but not including 1.2.2, and 1.4.0.dev4 up to but not including 1.4.0rc2, contain a vulnerability where an attacker can cause arbitrary module imports via the ray_pkg_version OmegaConf resolver. This allows execution of import-time side effects by supplying crafted configuration or command-line input.
CVE-2026-100721 is a critical vulnerability in the vm2 sandbox used within Red Hat Ansible Automation Platform 2.2's bootable container image. The flaw allows an attacker running untrusted guest code inside the sandbox to escape isolation and execute arbitrary code on the host system by exploiting improper enforcement of file path boundaries in a custom external module resolver. This leads to full compromise of confidentiality, integrity, and availability of the host. The vulnerability requires specific architectural conditions and is not exposed in Red Hat Developer Hub configurations. No patch or mitigation meeting Red Hat's criteria is currently available.
A vulnerability in the Node.js DNS resolver APIs allows hostnames containing embedded NUL characters to be truncated during resolution, potentially causing applications to resolve and act on unintended hostnames. This flaw affects Red Hat Hardened Images RPMs that include Node.js components. Exploitation requires an attacker to supply a hostname with an embedded NUL character to the dns.resolve API, and the application must rely on the resolved records. The issue can lead to confidentiality and integrity impacts comparable to connecting to a wrong host. Red Hat has released updated RPMs addressing this issue.
CVE-2026-19630 is a vulnerability in ISC BIND 9 DNS resolver where specially crafted inbound DNS messages with a particular structure cause excessive CPU and memory consumption. This occurs because BIND imposes no limit on processing these structures, leading to inefficient algorithmic complexity. The issue affects multiple BIND 9 versions from 9.11.0 through 9.21.26 and their corresponding S1 variants.