Skip to main content
VulnerabilityPublished

CVE-2026-92822: libmodulemd security update

Affects libmodulemdSource GCVE Database

0
Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-92822· Medium 6.2

Not known to be exploited · CVSS 6.2 Medium : upgrade to 2.15.0-2.oe2403sp3 when convenient.

Data as of 11 Nov 2026, 14:33 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.16.2
Patch
Available – fixed in 2.15.0-2.oe2403sp3
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 11 Nov 2026.

What to do

Upgrade libmodulemd to 2.15.0-2.oe2403sp3.

Affected software

ProductAffectedFixed in
openEuler 24.03-LTS-SP3libmodulemdpkg:rpm/openEuler/libmodulemd&distro=openEuler-24.03-LTS-SP3Other threatsAffected
  • <2.15.0-2.oe2403sp3
Fixed in
  • 2.15.0-2.oe2403sp3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in libmodulemd version 2.15.0-2.oe2403sp3 that addresses these vulnerabilities. Users should upgrade to this fixed version to remediate the issues. No additional mitigation steps are indicated by the vendor advisory.

Description

Multiple denial of service vulnerabilities were found in libmodulemd prior to version 2.15.0-2.oe2403sp3. These include stack exhaustion from deeply nested YAML xmd fields, excessive resource consumption from unbounded decompression of compressed YAML, and an out-of-bounds read during YAML serialization caused by incorrect loop bounds in rpm-map emission. These flaws can cause crashes or excessive CPU and memory usage.

References

Community reviews

Loading reviews…