Skip to main content
Menu
CVEs

Red Hat arbitrary file read in OpenSCAP offline scanning

Affects OpenSCAP offline scans of untrusted container or VM filesystem images on Red Hat Enterprise Linux 6, 7, 8, 9 and 10 and Red Hat Hardened Images. No fixed version is listed.

CVE-2026-126631Published November 19, 2026, updated

7.1HighCNA
Exploited
No known exploitation
Fix
See vendor advisory
Who is exposed
Specific setups only

Summary

OpenSCAP, as used in Red Hat Enterprise Linux 6, 7, 8, 9 and 10 and Red Hat Hardened Images, can be tricked during offline scans of untrusted images into following symbolic links that point outside the image. A local attacker who supplies a crafted container or VM disk image and gets it scanned, which requires a user to run the scan, can read sensitive files on the host and alter compliance results.

Written by a model

Original description

A flaw was found in OpenSCAP. This vulnerability allows for information disclosure when performing offline scans of untrusted filesystem images, such as container images or virtual machine (VM) disks. Because the scanner does not properly restrict symbolic link (symlink) resolution to the target image's root directory, an attacker can supply a crafted image containing links pointing to files on the host system. When the scan runs, typically with elevated privileges, OpenSCAP follows these links to read sensitive host files and expose their contents in the scan report or manipulate compliance results.

Who should check

Teams running offline OpenSCAP scans against untrusted container or VM disk images on Red Hat Enterprise Linux or Red Hat Hardened Images hosts.

“The vulnerability specifically impacts offline scanning pipelines where symlinks inside an inspected filesystem image escape the target directory”

access.redhat.com

What to do

  1. Check whether your setup matches what the bug needs.

    Offline scanning of an untrusted filesystem image (container image or VM disk). Scan runs in PROBE_OFFLINE_OWN mode.
  2. Workaround: Avoid running offline OpenSCAP scans against untrusted container or VM filesystem images directly on sensitive host systems; use an isolated sandbox such as a disposable container or VM instead.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-126631 (Openscap: symlink escape in offline scanning mode allows reading host files outside the scanned root), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126631 (entry last updated 2026-11-19):
Affected:
- Red Hat Red Hat Enterprise Linux 10: version range not reported
- Red Hat Red Hat Enterprise Linux 6: version range not reported
- Red Hat Red Hat Enterprise Linux 7: version range not reported
- Red Hat Red Hat Enterprise Linux 8: version range not reported
- Red Hat Red Hat Enterprise Linux 9: version range not reported
- Red Hat Red Hat Hardened Images: version range not reported
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Offline scanning of an untrusted filesystem image (container image or VM disk). (source: https://bugzilla.redhat.com/show_bug.cgi?id=2571597)
- Scan runs in PROBE_OFFLINE_OWN mode. (source: https://bugzilla.redhat.com/show_bug.cgi?id=2571597)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: local access, no login, a user action.
Workaround: Avoid running offline OpenSCAP scans against untrusted container or VM filesystem images directly on sensitive host systems; use an isolated sandbox such as a disposable container or VM instead. (source: https://www.cve.org/CVERecord?id=CVE-2026-126631)
CISA KEV: CVE-2026-126631 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126631 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://bugzilla.redhat.com/show_bug.cgi?id=2571597
- https://access.redhat.com/security/cve/CVE-2026-126631
- https://www.cve.org/CVERecord?id=CVE-2026-126631
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126631
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126631"}.

Affected versions

cve.now Index

27Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure5/25Specific setups only
  • Reach10/20Shipped in major Linux distributions
  • Severity7.1/10CVSS 7.1
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 77 if added to CISA KEV
  • Would score about 72 if CISA's SSVC rates exploitation active
  • Would score about 37 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-126631
RecordNVD · CVE-2026-126631
Write-ups 1Establishes: Technical detail and context.
Reportbugzilla.redhat.com · show_bug.cgi?id=2571597
Other links 1
Linkaccess.redhat.com · security/cve/CVE-2026-126631

Questions about CVE-2026-126631

Is CVE-2026-126631 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

When OpenSCAP runs an offline scan of an untrusted filesystem image, a symlink inside the image can point outside the scanned root. The scan can then read host files and include their contents in the results, or alter compliance results.

Source: bugzilla.redhat.com, access.redhat.com, cve.org

Am I affected, and how do I check?

The issue applies to offline scans of untrusted filesystem images, such as container images or VM disks, run in PROBE_OFFLINE_OWN mode. The listed products are Red Hat Enterprise Linux 6, 7, 8, 9 and 10 and Red Hat Hardened Images, with no version ranges given.

Source: bugzilla.redhat.com, access.redhat.com, cve.org

How do I fix CVE-2026-126631?

The advisory data lists no fixed versions and no patch identifiers. The only guidance given is to avoid running offline OpenSCAP scans of untrusted container or VM filesystem images directly on sensitive host systems.

Source: bugzilla.redhat.com, access.redhat.com, cve.org

What if there's no patch?

Until a fix is available, run offline scans of untrusted images in an isolated sandbox, such as a disposable container or VM, rather than directly on sensitive host systems.

Source: bugzilla.redhat.com, access.redhat.com, cve.org

No corrections so far. Something wrong on this page? Report an error.