VulnerabilityPublished 21 Oct 2026Updated 6 Nov 2026

CVE-2026-92822: libmodulemd · CWE-674

Source GCVE Database

Compare

Authoritative record:CVE-2026-92822· Medium 6.2

Not known to be exploited · CVSS 6.2 Medium.

Data as of 6 Nov 2026, 04:32 UTC

CVSS 3.1 base score

6.2Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (redhat)	CVSS 3.1	6.2

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-85r9-7wj5-x6x5

What to do

Affected software

Product	Affected	Fixed in
Red Hat Enterprise Linux 10libmodulemd	Affected–	Fixed in–
Red Hat Enterprise Linux 8libmodulemd	Affected–	Fixed in–
Red Hat Enterprise Linux 9libmodulemd	Affected–	Fixed in–
Red Hat Hardened Imageslibmodulemd	Affected–	Fixed in–
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8	Affected–	Fixed in–
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9	Affected–	Fixed in–

AI-suggested

Avoid parsing untrusted modulemd documents containing attacker-controlled xmd data. If such input must be accepted, implement checks to reject unusually deep or large xmd structures before passing them to libmodulemd. Additionally, isolate parsing in a process with strict limits on stack size, CPU, and memory usage.

Description

A vulnerability in libmodulemd allows denial of service via stack exhaustion or excessive resource consumption when parsing deeply nested xmd YAML content. This occurs because the parser uses recursive YAML mapping and sequence helpers without limits on recursion depth or node count. Exploitation requires processing attacker-controlled modulemd YAML with deeply nested xmd structures. The flaw impacts availability only and does not affect confidentiality or integrity. Environments that only process trusted module metadata are not practically exposed. Mitigation involves avoiding untrusted input or limiting resource usage during parsing.

Impact

The vulnerability allows an attacker who can supply crafted modulemd YAML with deeply nested xmd content to cause denial of service by exhausting stack or other resources during parsing. This results in application or process crashes, impacting availability. There is no confidentiality or integrity impact. Exploitation requires local access to parse attacker-controlled input. Environments that only ingest trusted module metadata are not practically exposed.

Summary

CVE-2026-92822 is a denial of service vulnerability in libmodulemd caused by unbounded recursion when parsing the xmd field in module metadata YAML. The xmd field is converted into nested GVariant values through recursive YAML mapping and sequence helpers without any recursion-depth or node-count limits. An attacker supplying crafted modulemd YAML with deeply nested xmd content can cause stack exhaustion or excessive resource consumption, leading to application or process termination. The vulnerability affects availability only, with no impact on confidentiality or integrity. Exploitation requires local access to parse malicious modulemd YAML. The vulnerability is tracked as CWE-674 (Uncontrolled Recursion).

CWE-674Uncontrolled Recursion (opens in a new tab)
Class weakness
The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.
Implementation
Ensure that an end condition will be reached under all logic conditions. The end condition may include checking against the depth of recursion and exiting with an error if the recursion goes too deep. The complexity of the end condition contributes to the effectiveness of this action.
Implementation
Increase the stack size.
Attack patterns
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Nov 2026, 04:32 UTC

WeaknessesCWE-674

Technical details

References

Community reviews

Related threats