Live › vulnerability › CVE-2026-92822
Go to dashboardlibmodulemd parses the xmd field of module metadata into nested GVariant values using recursive helpers with no depth or node-count limit. A crafted modulemd YAML file with deeply nested xmd content can exhaust the stack or consume excessive resources, causing a denial of service.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Systems that parse untrusted modulemd YAML metadata with libmodulemd, such as tools that ingest module repositories from third parties. Sources do not name fixed versions or specific distributions. Teams that only consume their own or vendor-trusted module metadata are less exposed.
No product ranges from the sources yet.
Unknown from the sources.
Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
A flaw was found in libmodulemd. When parsing module metadata, the xmd field is converted into nested GVariant values through recursive YAML mapping and sequence helpers without a recursion-depth or node-count limit. An attacker who can supply crafted modulemd YAML with deeply nested xmd content can cause stack exhaustion or excessive resource consumption, resulting in a denial of service.
This page as .md · .json · in your agent: get_signal("CVE-2026-92822")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.