Skip to content
VulniPulse
Advisory severityMedium5.3Red Hat Linux

Medium [CVE-2026-50162] File store write outside working directory via symlink traversal

This medium-severity Red Hat Linux advisory covers CVE-2026-50162 affecting Migration Toolkit for Virtualization 2.10, Migration Toolkit for Virtualization 2.11, OpenShift Security Profiles Operator 1.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-50162 Source published Source updated

VulniPulse record published Record updated

CVE-2026-50162
Affected products & platforms
Red Hat LinuxUnclassified
Open source advisory

Summary

oras-go is a Go library for managing OCI artifacts. Prior to 2.6.1, resolveWritePath() in content/file/file.go uses a lexical filepath.

Rel check for workingDir and does not account for symlink traversal, so when AllowPathTraversalOnWrite=false an attacker-controlled blob title through ocispec. AnnotationTitle such as out/pwn.txt can follow a workingDir symlink out -> /some/outside/dir and cause pushFile() to create /some/outside/dir/pwn.txt outside workingDir.

This issue is fixed in version 2.6.1. A flaw was found in oras-go.

The file content store, intended to confine writes to a specified working directory, does not properly account for symbolic link (symlink) traversal. A remote attacker, by providing a specially crafted blob title, could exploit this vulnerability to create files outside the intended working directory.

This filesystem boundary bypass allows for arbitrary file creation, potentially leading to unauthorized data modification or system compromise depending on the runtime environment. Red Hat severity: Moderate — CVSS 5.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N).

Weakness: CWE-22.

Affected products named by the advisory: Migration Toolkit for Virtualization 2.10; Migration Toolkit for Virtualization 2.11; OpenShift Security Profiles Operator 1; Red Hat Edge Manager 1.1; and 18 more.

Is CVE-2026-50162 exploited?

No exploitation is reported in the sources VulniPulse tracks: CVE-2026-50162 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.

How do I fix CVE-2026-50162?

Upgrade to a fixed release named by Red Hat:

  • 2.6.1
  • migration-toolkit-virtualization/mtv-validation-rhel9:1791228247
  • migration-toolkit-virtualization/mtv-validation-rhel9:1791229031
  • compliance/openshift-security-profiles-operator-bundle:1790626888
  • compliance/openshift-security-profiles-rhel8-operator:1790623030
  • rhem/flightctl-alert-exporter-rhel10:1789485396
  • rhem/flightctl-alertmanager-proxy-rhel10:1789486842
  • rhem/flightctl-api-rhel10:1789485939
  • rhem/flightctl-cli-artifacts-rhel10:1789488001
  • rhem/flightctl-db-setup-rhel10:1789487240
  • rhem/flightctl-imagebuilder-api-rhel10:1789486040
  • rhem/flightctl-imagebuilder-worker-rhel10:1789486782

38 more fixed releases are listed below.

Confirm against the vendor advisory before you patch.

Affected versions
  • < 2.6.1

Official advisory · high-confidence parse· fetched 11 days ago·verify at source

Fixed versions
  • 2.6.1
  • migration-toolkit-virtualization/mtv-validation-rhel9:1791228247
  • migration-toolkit-virtualization/mtv-validation-rhel9:1791229031
  • compliance/openshift-security-profiles-operator-bundle:1790626888
  • compliance/openshift-security-profiles-rhel8-operator:1790623030
  • rhem/flightctl-alert-exporter-rhel10:1789485396
  • rhem/flightctl-alertmanager-proxy-rhel10:1789486842
  • rhem/flightctl-api-rhel10:1789485939
  • rhem/flightctl-cli-artifacts-rhel10:1789488001
  • rhem/flightctl-db-setup-rhel10:1789487240
  • rhem/flightctl-imagebuilder-api-rhel10:1789486040
  • rhem/flightctl-imagebuilder-worker-rhel10:1789486782
  • rhem/flightctl-pam-issuer-rhel10:1789487151
  • rhem/flightctl-periodic-rhel10:1789485633
  • rhem/flightctl-telemetry-gateway-rhel10:1789486686
  • rhem/flightctl-userinfo-proxy-rhel10:1789487947
  • rhem/flightctl-worker-rhel10:1789486071
  • rhem/flightctl-alert-exporter-rhel9:1789488080
  • rhem/flightctl-alertmanager-proxy-rhel9:1789486160
  • rhem/flightctl-api-rhel9:1789487080
  • rhem/flightctl-cli-artifacts-rhel9:1789485800
  • rhem/flightctl-db-setup-rhel9:1789487116
  • rhem/flightctl-imagebuilder-api-rhel9:1789486154
  • rhem/flightctl-imagebuilder-worker-rhel9:1789485338
  • rhem/flightctl-pam-issuer-rhel9:1789486466
  • rhem/flightctl-periodic-rhel9:1789486513
  • rhem/flightctl-telemetry-gateway-rhel9:1789485664
  • rhem/flightctl-userinfo-proxy-rhel9:1789485648
  • rhem/flightctl-worker-rhel9:1789486829
  • rhem/flightctl-alert-exporter-rhel10:1789485358
  • rhem/flightctl-alertmanager-proxy-rhel10:1789485956
  • rhem/flightctl-api-rhel10:1789485653
  • rhem/flightctl-cli-artifacts-rhel10:1789486382
  • rhem/flightctl-db-setup-rhel10:1789487147
  • rhem/flightctl-imagebuilder-api-rhel10:1789485823
  • rhem/flightctl-imagebuilder-worker-rhel10:1789485526
  • rhem/flightctl-pam-issuer-rhel10:1789487060
  • rhem/flightctl-periodic-rhel10:1789486651
  • rhem/flightctl-telemetry-gateway-rhel10:1789486468
  • rhem/flightctl-userinfo-proxy-rhel10:1789486659
  • rhem/flightctl-worker-rhel10:1789486740
  • RHSA-2026:83663
  • RHSA-2026:83662
  • RHSA-2026:76752
  • RHSA-2026:68044
  • RHSA-2026:68253
  • RHSA-2026:68006
  • RHSA-2026:68254
  • RHSA-2026:42230
  • RHSA-2026:42241

Official advisory · high-confidence parse· fetched 11 days ago·verify at source

Mitigation

Upgrade to a fixed release: 2.6.1, migration-toolkit-virtualization/mtv-validation-rhel9:1791228247, migration-toolkit-virtualization/mtv-validation-rhel9:1791229031, compliance/openshift-security-profiles-operator-bundle:1790626888, compliance/openshift-security-profiles-rhel8-operator:1790623030, rhem/flightctl-alert-exporter-rhel10:1789485396. That is the remediation for this advisory.

The vendor advisory may list interim mitigations or workarounds not captured here. Review it before change work.

Official advisory · high-confidence parse· fetched 11 days ago·verify at source

Get an email when Red Hat publishes the next one.

See Red Hat's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Red Hat
All Red Hat Linux advisories

iPhone and Android apps · New on the App Store

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.