Skip to main content
Vulnerability Database/CVE-2026-85518

CVE-2026-85518: OpenSCAP Path Traversal Vulnerability

CVE-2026-85518 is a path traversal vulnerability in OpenSCAP that allows attackers to create or modify files outside intended directories. This article covers technical details, affected versions, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-85518 Overview

A path traversal vulnerability [CWE-22] exists in OpenSCAP, the open source library and toolset for implementing Security Content Automation Protocol (SCAP) workflows. The flaw occurs when the application decomposes a Source DataStream (SDS) file. OpenSCAP does not properly validate relative file path attributes contained within the datastream.

An attacker who tricks a user or automated system into decomposing a crafted datastream can trigger directory traversal sequences. Successful exploitation allows unauthorized file creation or modification outside the intended target directory, running with the permissions of the executing process.

Critical Impact

Processing a malicious SDS file can write or overwrite arbitrary files on the host, with integrity impact rated High and limited availability impact.

Affected Products

  • OpenSCAP library and command-line tooling
  • Red Hat distributions shipping OpenSCAP (see vendor advisory)
  • Automated compliance scanning pipelines consuming untrusted SDS files

Discovery Timeline

  • 2026-10-21 - CVE-2026-85518 published to NVD
  • 2026-10-22 - Last updated in NVD database

Technical Details for CVE-2026-85518

Vulnerability Analysis

OpenSCAP uses Source DataStream (SDS) files to bundle multiple SCAP components, including XCCDF benchmarks, OVAL definitions, and CPE dictionaries, into a single XML container. The oscap ds sds-decompose operation extracts these components to the filesystem using path attributes declared inside the datastream.

The decomposition routine trusts the relative file path attributes supplied by the datastream without canonicalizing or constraining them to the output directory. A crafted SDS file can embed ../ sequences or absolute paths in these attributes. When the component is written to disk, the resulting file path escapes the intended extraction directory.

The process writes files with the privileges of the invoking user. Automated compliance tooling frequently runs OpenSCAP as root during host scans, which expands the integrity impact to system binaries, cron entries, and configuration files.

Root Cause

The root cause is missing input validation on filename and path attributes within SDS XML components. The decomposition logic concatenates the attacker-controlled relative path with the target directory. It does not reject traversal sequences or verify that the resolved path remains within the intended base directory, violating the containment property expected of archive-like extraction routines.

Attack Vector

Exploitation requires local access and user interaction. An attacker delivers a malicious SDS file to a victim through email, a shared repository, or a compromised content feed. When the victim or an automated job runs oscap ds sds-decompose against the file, OpenSCAP writes component contents to attacker-chosen locations.

Full technical details are available in the Red Hat CVE-2026-85518 Advisory and the Red Hat Bug Report #2478522.

Detection Methods for CVE-2026-85518

Indicators of Compromise

  • SDS XML files containing ../ sequences or absolute paths in component href or filename attributes.
  • Files created outside the expected OpenSCAP output directory shortly after an oscap ds sds-decompose invocation.
  • Modifications to sensitive paths such as /etc/, /usr/bin/, or user ~/.ssh/ coinciding with SCAP scanning jobs.

Detection Strategies

  • Inspect SDS files statically for suspicious path attributes before processing them with OpenSCAP.
  • Audit shell history and job logs for oscap invocations referencing untrusted datastream sources.
  • Correlate filesystem change events with OpenSCAP process execution to identify writes outside the designated working directory.

Monitoring Recommendations

  • Enable Linux audit rules on openat and creat syscalls originating from the oscap binary.
  • Forward OpenSCAP execution telemetry and filesystem events to a central analytics platform for correlation.
  • Alert when OpenSCAP processes write to directories outside explicitly allowed output paths.

How to Mitigate CVE-2026-85518

Immediate Actions Required

  • Apply the OpenSCAP update published through your Linux distribution as soon as it is available.
  • Treat all externally sourced SDS files as untrusted and validate their contents before decomposition.
  • Run oscap under a dedicated, least-privileged service account rather than root where feasible.

Patch Information

Refer to the Red Hat CVE-2026-85518 Advisory for fixed package versions and backports. Rebuild or redistribute any container images and golden images that embed vulnerable OpenSCAP binaries after patching.

Workarounds

  • Decompose SDS files only inside disposable sandboxes such as containers or ephemeral VMs with no sensitive mounts.
  • Restrict OpenSCAP file system access using mandatory access controls such as SELinux or AppArmor profiles.
  • Pre-validate SDS XML with a trusted parser that rejects path attributes containing .. or absolute path prefixes.
bash
# Configuration example: run oscap in a confined working directory
install -d -m 0700 /var/tmp/oscap-sandbox
cd /var/tmp/oscap-sandbox
sudo -u scap-runner oscap ds sds-decompose /path/to/untrusted.xml ./out/

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.