# CVE-2026-92824: Libmodulemd: libmodulemd: out-of-bounds read when emitting rpm-map artifacts


- **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:** 26 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-92824, GHSA-j65x-29mg-x4cj, UBUNTU-CVE-2026-92824

## What is CVE-2026-92824?

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

### Official description

A flaw was found in libmodulemd. In the module stream v2 rpm-map emission path, an inner loop incorrectly uses the count of digest algorithms as its bound instead of the number of checksums in the current digest table. Crafted modulemd v2 metadata with multiple digest types can trigger an out-of-bounds read during YAML serialization, typically causing a crash and resulting in a denial of service.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2026-92824 being exploited?

There is no known exploitation of CVE-2026-92824 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92824 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-92824 in the wild and no public exploit code.

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-92824/ (Markdown: https://insights.sbomify.com/CVE-2026-92824/index.md)
```

## Sources

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

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