Summary
yggdrasil is a system daemon that subscribes to topics on an MQTT broker and routes any data received on the topics to an appropriate child "worker" process, exchanging data with its worker processes through a D-Bus message broker.
Security Fix(es):
* mime: golang: Golang MIME: Denial of Service via maliciously-crafted MIME header (CVE-2026-42504)
* encoding/asn1: golang: Go encoding/asn1: Denial of Service via excessive recursion in Unmarshal (CVE-2026-33818)
* net/url: golang: golang net/url: Denial of Service from quadratic complexity in path resolution (CVE-2026-56860)
* crypto/tls: golang: Golang crypto/tls: Denial of Service via indefinite KeyUpdate messages (CVE-2026-56862)
* encoding/xml: golang: Go: Denial of Service via XML decoding recursion depth issue (CVE-2026-56859)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Fixed packages 2
| Release | Package | Fixed in |
|---|---|---|
| AlmaLinux · 10 | yggdrasil | 0.4.9.2-1.el10_2.3 |
| AlmaLinux · 10 | yggdrasil-devel | 0.4.9.2-1.el10_2.3 |
Vulnerabilities 5
-
High 7.5
Enforce maximum recursion depth in encoding/asn1
Enforce a recursion limit in Unmarshal to prevent stack exhaustion when parsing deeply-nested, recursive structures.
-
High 7.5
Quadratic complexity in WordDecoder.DecodeHeader in mime
Decoding a maliciously-crafted MIME header containing many invalid encoded-words can consume excessive CPU.
-
High 7.5
Add recursion depth guard during decode in encoding/xml
Previously, DecodeElement would reset the depth counter causing it to never fire; this could lead to stack exhaustion.
-
High 7.5
Limit handshake messages we are willing to accept post-handshake in crypto/tls
Handshake messages, such as KeyUpdate, are always considered as state-advancing, regardless of whether a handshake has been completed or not. As a result, a malicious client can keep sending KeyUpdate messages to force the server to keep performing key deriva…
-
Medium 5.9
Avoid quadratic complexity in resolvePath in net/url
Previously, resolving relative paths containing parent directory ('..') segments performed string conversions and buffer rewrites on each step, resulting in quadratic time complexity and high memory allocation overhead. Now, path resolution operates on a byte…
References
-
report
https://access.redhat.com/security/cve/CVE-2026-33818
-
report
https://access.redhat.com/security/cve/CVE-2026-42504
-
report
https://access.redhat.com/security/cve/CVE-2026-56859
-
report
https://access.redhat.com/security/cve/CVE-2026-56860
-
report
https://access.redhat.com/security/cve/CVE-2026-56862
-
report
https://bugzilla.redhat.com/2484204
-
report
https://bugzilla.redhat.com/2515815
-
report
https://bugzilla.redhat.com/2515820
-
report
https://bugzilla.redhat.com/2515839
-
report
https://bugzilla.redhat.com/2515840
-
advisory
https://errata.almalinux.org/10/ALSA-2026-69308.html