# CVE-2026-122056: Openscap: one-byte heap buffer overflow in sds-compose may lead to denial-of-service


- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 11 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-122056, ECHO-82e5-517a-1652, GHSA-qvvp-v7hp-wr62, UBUNTU-CVE-2026-122056

## What is CVE-2026-122056?

CVE-2026-122056 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 9 Nov 2026. 

### Official description

A flaw was found in OpenSCAP. A heap-based buffer overflow can occur when processing a specially crafted Extensible Configuration Checklist Description Format (XCCDF) document using the sds-compose option. An attacker could exploit this vulnerability to corrupt memory, resulting in an application crash and a Denial of Service (DoS).

Weakness: CWE-787 (Out-of-bounds Write)

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


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

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

## Is CVE-2026-122056 being exploited?

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

Public exploit code:

- A flaw was found in OpenSCAP. A heap-based buffer overflow can occur when processing a specially crafted XCCDF document. (github_poc): https://github.com/D7EAD/CVE-2026-122056

## Fix prompt for AI coding agents

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

What it is: CVE-2026-122056 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-122056 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-122056/ (Markdown: https://insights.sbomify.com/CVE-2026-122056/index.md)
```

## Sources

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

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