<?xml version="1.0" encoding="utf-8"?>
  <?xml-stylesheet type="text/xsl" href="sa-render.xsl"?>
  <update from="huaweicloud.com" type="security" status="stable" version="1">
    <id>HCE3-SA-2026-0486</id>
    <title>An update for unbound is now available for HCE 3.0</title>
    <severity>Critical</severity>
    <release>HCE 3.0</release>
    <issued date="2026-10-23 07:34:06"/>
    <updated date="2026-10-23 07:34:06"/>
    <references>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2026-81634" id="CVE-2026-81634" title="CVE-2026-81634 Base Score: 7.5 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2026-82720" id="CVE-2026-82720" title="CVE-2026-82720 Base Score: 5.9 Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2026-77955" id="CVE-2026-77955" title="CVE-2026-77955 Base Score: 4.4 Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:N" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2026-82717" id="CVE-2026-82717" title="CVE-2026-82717 Base Score: 9.8 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2026-77860" id="CVE-2026-77860" title="CVE-2026-77860 Base Score: 3.7 Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2026-81642" id="CVE-2026-81642" title="CVE-2026-81642 Base Score: 9.8 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2026-85501" id="CVE-2026-85501" title="CVE-2026-85501 Base Score: 7.5 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2026-56444" id="CVE-2026-56444" title="CVE-2026-56444 Base Score: 5.9 Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2026-80225" id="CVE-2026-80225" title="CVE-2026-80225 Base Score: 7.5 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H" type="cve"/>
    </references>
    <description>Security Fix(es):

In NLnet Labs Unbound up to and including 1.26.0, a 255 length query name with a large TCP response can lead to a heap buffer overflow during the RRSet canonicalisation routine. This is caused by missing to add the first owner name into the buffer length check. A malicious actor operating a malicious name server or tampering with an incoming response to Unbound (canonicalisation happens before DNSSEC validation), can trigger the vulnerability. (CVE-2026-81634)

NLnet Labs Unbound 1.12.0 up to and including 1.26.0 has a use-after-free vulnerability when compiled for DNS-over-HTTPs support with _x27;--with-libnghttp2_x27;. During failure code paths (i.e., RPZ drop query, jostle due to heavy traffic), a dropped DoH stream brings down the whole DoH session and does not account properly for other DoH streams in the same session. This leads to use-after-free in those code paths. If the prerequisites are satisfied (possible RPZ drop or heavy client traffic), a malicious actor can trigger the vulnerability with a single DoH connection and the appropriate traffic. Impact is limited as the reads are not user controlled and the use-after-free leads to early returns. However, a hardened allocator can catch the use-after-free and controllably terminate the process resulting to denial of service. (CVE-2026-82720)

In NLnet Labs Unbound 1.13.2 up to and including 1.26.1, a vulnerability in ZONEMD configured zones (zonemd-check: yes) which are located below (but not at) a trust anchor allow for an attack window where (tampered with) zone contents are served (or stored to disk) prior to the ZONEMD integrity check. This is caused by the needed DS/DNSKEY asynchronous resolution that needs to happen before the ZONEMD check completes. If a zonefile is written to disk (zonefile: option) while the ZONEMD check failed, the tampered data are reloaded on startup and available until ZONEMD verification concludes again. If verification fails, the data is not served any more but still persists on disk for future reloads. (CVE-2026-77955)

In NLnet Labs Unbound up to and including 1.26.0, a vulnerability was found in that can progressively corrupt heap memory and under certain systems and compilation options could lead to remote code execution. The vulnerability starts when CNAME synthesis during an upstream response needs to enforce(rewrite) a max TTL value in the packet buffer. Coupled with a compression pointer that points to the overwritten value and invalidates the domain name, it leads to an error path that does not properly move the buffer position and allows for the heap buffer overflow. Since this is heavily reliant on heap memory layout, results are memory corruption that eventually leads to a crash and under specific systems and compilation options remote code execution. (CVE-2026-82717)

In NLnetLabs Unbound 1.20.0 up to and including 1.26.0, a vulnerability on the _x27;serve-expired_x27; code path can cause a double decrement on the _x27;wait-limit_x27; counter per client IP essentially bypassing one of the counter measures that was introduced for DNSBomb (CVE-2024-33655). A malicious actor can exploit this by controlling an authoritative zone with short TTL, so cached entries expire quickly. Each _x27;slow_x27; query, one the attacker_x27;s authoritative never answers, is followed by one query for an expired cached name, which is answered immediately via the _x27;serve-expired_x27; path and decrements the counter twice. This second query was named _x27;pump_x27;. By alternating slow queries and pumps, the attacker keeps the per-client counter at or below the configured _x27;wait-limit_x27; indefinitely, and can hold an arbitrary number of pending queries from a single source IP, up to the global mesh quota (num-queries-per-thread); eventually bypassing one of the counter measures introduced for DNSBomb (CVE-2024-33655). This vulnerability is present on the _x27;serve-expired_x27; code path. (CVE-2026-77860)

In NLnet Labs Unbound up to and including 1.26.0, a vulnerability was found in the DNSSEC validator that enables denial of service and possible remote code execution as a result of digesting DNSKEYs. A DNSKEY with an owner compression pointer to its own RDATA can overflow the digest buffer. Remote code execution is possible through attacker controlled data. An adversary can exploit the vulnerability by controlling a malicious zone and querying a vulnerable Unbound. (CVE-2026-81642)

Novel vulnerabilities to launch algorithmic complexity attacks on DNSSEC have been researched under the term _x27;ReTrap_x27;. These result in degradation of service when malicious zones are used to serve the algorithmic complexity vulnerabilities. NLnet Labs Unbound up to and including 1.26.0 is vulnerable to some of them. TagTrap, where  the triple(Zone, Algo, KeyTag) matching mechanism introduces a significant attack vector when resolvers handle malicious responses containing numerous mismatched DNSKEY, RRSIG, and DS record. DelegationTrap, where constructing the chain-of-trust requires iterative validation of DNSKEY and DS records from the root zone downward. For deeply nested domains, this results in significant computational overhead. NsecTrap, where  responses with excessive invalid NSEC records compel the resolver to validate each one. AdditionalTrap, where Unbound by default would try to DNSSEC validate the ADDITIONAL section as well. This can be exploited to waste validation resources by malicious users. (CVE-2026-85501)

In NLnet Labs Unbound 1.20.0 up to and including 1.25.1, when Unbound is configured with _x27;serve-expired: yes_x27; and _x27;serve-expired-client-timeout &gt; discard-timeout &gt; 0_x27; (contrary to the suggested values), the discard-timeout branch during the serve expired logic drops an aged client reply without performing the correct accounting for the number of reply addresses for the query. Other identical branches outside of serve expired perform the correct decrement. Since the counter is never decremented in such scenario, it can reach the maximum limit and new clients for duplicate in-flight queries are silently dropped resulting in degradation of resolution service. A malicious actor can exploit the vulnerability by querying the resolver for a client-controlled slow-on-demand authoritative zone that can drive the counter past the threshold. Shipped defaults for _x27;serve-expired-client-timeout: 1800_x27; and _x27;discard-timeout: 1900_x27; make the branch unreachable. (CVE-2026-56444)

In NLnetLabs Unbound up to and including 1.26.0, a degradation of service vulnerability is present in the TCP/DoT reading procedure where there is no limit on consecutive reads. A malicious actor that can stream and sustain a rate of distinct uncached names over the TCP/DoT connection, monopolizes a single worker_x27;s entire event loop for as long as its writes stay ahead of the drain. (CVE-2026-80225)
</description>
    <pkglist>
      <collection short="HCE 3.0" package="unbound">
        <name>HCE 3.0</name>
        <package arch="x86_64" name="python3-unbound" version="1.17.1" release="10.r9.hce3">
          <filename>python3-unbound-1.17.1-10.r9.hce3.x86_64.rpm</filename>
        </package>
        <package arch="x86_64" name="unbound-libs" version="1.17.1" release="10.r9.hce3">
          <filename>unbound-libs-1.17.1-10.r9.hce3.x86_64.rpm</filename>
        </package>
        <package arch="aarch64" name="python3-unbound" version="1.17.1" release="10.r9.hce3">
          <filename>python3-unbound-1.17.1-10.r9.hce3.aarch64.rpm</filename>
        </package>
        <package arch="aarch64" name="unbound-libs" version="1.17.1" release="10.r9.hce3">
          <filename>unbound-libs-1.17.1-10.r9.hce3.aarch64.rpm</filename>
        </package>
      </collection>
    </pkglist>
  </update>
