# CVE-2026-92822: Libmodulemd: libmodulemd: unbounded recursion when parsing nested xmd yaml


- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-92822, GHSA-85r9-7wj5-x6x5, UBUNTU-CVE-2026-92822

## What is CVE-2026-92822?

CVE-2026-92822 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 21 Oct 2026. 

### Official description

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.

Weakness: CWE-674 (Uncontrolled Recursion)

## Which versions are affected by CVE-2026-92822?


## How do I fix CVE-2026-92822?

No fix has been published for CVE-2026-92822 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-92822 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92822 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92822 and fix it if it is affected.

What it is: CVE-2026-92822 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 21 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92822 exists.

Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92822/ (Markdown: https://insights.sbomify.com/CVE-2026-92822/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92822
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92822
- OSV: https://osv.dev/vulnerability/CVE-2026-92822

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92822/
Summaries are generated and may contain mistakes; the official description above is the record.