# CVE-2026-85518: Openscap: openscap: arbitrary file write via path traversal in source datastream decomposition


- **Severity:** Medium 6.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 21 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-85518, ECHO-2455-2827-339c, GHSA-vp9g-975v-q4cm, openSUSE-SU-2026:12249-1

## What is CVE-2026-85518?

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

### Official description

A flaw was found in OpenSCAP. When decomposing a Source DataStream (SDS) file, the application does not properly validate relative file path attributes, leading to a path traversal vulnerability. An attacker can exploit this flaw by tricking a user or automated system into decomposing a crafted datastream containing directory traversal sequences. Successful exploitation allows unauthorized file creation or modification outside the intended target directory with the permissions of the executing process.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openscap` | openSUSE:Tumbleweed | All versions | 1.4.6-1.1 |

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

Upgrade to a fixed version.

## Is CVE-2026-85518 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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