Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.
Patch available
Direct vendor intelligence
Authoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
The vendor explicitly identifies these products as affected by this CVE.
ansible-automation-platform-26/eda-controller-rhel9 as a component of Red Hat Ansible Automation Platform 2
ansible-automation-platform-27/eda-controller-rhel9 as a component of Red Hat Ansible Automation Platform 2
podman as a component of Red Hat Enterprise Linux 10
podman-docker as a component of Red Hat Enterprise Linux 10
podman-remote as a component of Red Hat Enterprise Linux 10
podman-tests as a component of Red Hat Enterprise Linux 10
podman.src as a component of Red Hat Enterprise Linux 10
podman-catatonit (container-tools:rhel8) as a component of Red Hat Enterprise Linux 8
podman-docker (container-tools:rhel8) as a component of Red Hat Enterprise Linux 8
podman-gvproxy (container-tools:rhel8) as a component of Red Hat Enterprise Linux 8
podman-manpages (container-tools:rhel8) as a component of Red Hat Enterprise Linux 8
podman-plugins (container-tools:rhel8) as a component of Red Hat Enterprise Linux 8
Summary
A flaw was found in Podman. A remote attacker can exploit this vulnerability by running a malicious container image where the WORKDIR (working directory) path contains a symbolic link (symlink). This can lead to the creation of a directory or modification of ownership on the host filesystem, potentially impacting system integrity.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
Optional official sources
National CERT insights ?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.
Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.
Official European source
ENISA European Vulnerability Database
Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.
1 current
ENISA EUVD identifier
EUVD-2026-39808
No EUVD known-exploited evidence
ENISA has published the identifier mapping but no EUVD description has been stored yet.
EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days
Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.
Patch available
01
What, why and how
Podman is a tool for managing OCI containers and pods. From 3.0.0 until 5.7.1, running a malicious container image where the WORKDIR path contains a symlink can create a directory or modify ownership on the host filesystem. Modified ownership is less likely to happen as that requires help from an untrusted/malicious process that mutates the host filesystem tree during dereferencing of the WORKDIR path, to trigger a race condition. This vulnerability is fixed in 5.7.1.
What
Podman is a tool for managing OCI containers and pods. From 3.0.0 until 5.7.1, running a malicious container image where the WORKDIR path contains a symlink can create a directory or modify ownership on the host filesystem. Modified ownership is less likely to happen as that requires help from an untrusted/malicious process that mutates the host filesystem tree during dereferencing of the WORKDIR path, to trigger a race condition. This vulnerability is fixed in 5.7.1.
Why
The product, when opening a file or directory, does not sufficiently account for when the file is a symbolic link that resolves to a target outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
Podman is a tool for managing OCI containers and pods. From 3.0.0 until 5.7.1, running a malicious container image where the WORKDIR path contains a symlink can create a directory or modify ownership on the host filesystem. Modified ownership is less likely to happen as that requires help from an untrusted/malicious process that mutates the host filesystem tree during dereferencing of the WORKDIR path, to trigger a race condition. This vulnerability is fixed in 5.7.1.
Why
The product, when opening a file or directory, does not sufficiently account for when the file is a symbolic link that resolves to a target outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation ?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No confirmed evidence
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material ?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.Reference recorded
A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.
Likely attack path
a network path → UNIX Symbolic Link (Symlink) Following → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness ?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-61: UNIX Symbolic Link (Symlink) Following. The product, when opening a file or directory, does not sufficiently account for when the file is a symbolic link that resolves to a target outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.
CVSS vector ?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.ILowIntegrity impact: A successful attack can cause a limited loss.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
Operational remediation based on structured source evidence.
Status ?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
ansible-automation-platform-26/eda-controller-rhel9 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-27/eda-controller-rhel9 as a component of Red Hat Ansible Automation Platform 2; podman as a component of Red Hat Enterprise Linux 10; podman-docker as a component of Red Hat Enterprise Linux 10; podman-remote as a component of Red Hat Enterprise Linux 10; podman-tests as a component of Red Hat Enterprise Linux 10; podman.src as a component of Red Hat Enterprise Linux 10; podman-catatonit (container-tools:rhel8) as a component of Red Hat Enterprise Linux 8; podman-docker (container-tools:rhel8) as a component of Red Hat Enterprise Linux 8; podman-gvproxy (container-tools:rhel8) as a component of Red Hat Enterprise Linux 8; podman-manpages (container-tools:rhel8) as a component of Red Hat Enterprise Linux 8; podman-plugins (container-tools:rhel8) as a component of Red Hat Enterprise Linux 8; podman-remote (container-tools:rhel8) as a component of Red Hat Enterprise Linux 8; podman-tests (container-tools:rhel8) as a component of Red Hat Enterprise Linux 8; podman.src (container-tools:rhel8) as a component of Red Hat Enterprise Linux 8; podman (container-tools:rhel8) as a component of Red Hat Enterprise Linux 8; podman as a component of Red Hat Enterprise Linux 9; podman-catatonit as a component of Red Hat Enterprise Linux 9; podman-docker as a component of Red Hat Enterprise Linux 9; podman-gvproxy as a component of Red Hat Enterprise Linux 9; podman-plugins as a component of Red Hat Enterprise Linux 9; podman-remote as a component of Red Hat Enterprise Linux 9; podman-tests as a component of Red Hat Enterprise Linux 9; podman.src as a component of Red Hat Enterprise Linux 9; openshift/ose-rhel-coreos-8 as a component of Red Hat OpenShift Container Platform 4; openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4; podman as a component of Red Hat OpenShift Container Platform 4; podman-catatonit as a component of Red Hat OpenShift Container Platform 4; podman-docker as a component of Red Hat OpenShift Container Platform 4; podman-gvproxy as a component of Red Hat OpenShift Container Platform 4; and 8 more
Fixed
podman-main@aarch64 as a component of Red Hat Hardened Images; podman-main@noarch as a component of Red Hat Hardened Images; podman-main@src as a component of Red Hat Hardened Images; podman-main@x86_64 as a component of Red Hat Hardened Images
Action
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 26 Jun 2026 · Last source change 26 Jun 2026, 18:31 UTC · CWE-61 · UNIX Symbolic Link (Symlink) Following
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source ?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-39808
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Affected versionsThe structured affected or fixed version information changed.
Before
ansible-automation-platform-26/eda-controller-rhel9 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-27/eda-controller-rhel9 as a component of Red Hat Ansible Automation Platform 2; podman as a component of Red Hat Enterprise Linux 10; podman-docker as a component of Red Hat Enterprise Linux 10; podman-remote as a component of Red Hat Enterprise Linux 10; podman-tests as a component of Red Hat Enterprise Linux 10; podman.src as a component of Red Hat Enterprise Linux 10; podman-catatonit (container-tools:rhel8) as a component of Red Hat Enterprise Linux 8; podman-docker (container-tools:rhel8) as a component of Red Hat Enterprise Linux 8; podman-gvproxy (container-tools:rhel8) as a component of Red Hat Enterprise Linux 8; podman-manpages (container-tools:rhel8) as a component of Red Hat Enterprise Linux 8; podman-plugins (container-tools:rhel8) as a component of Red Hat Enterprise Linux 8; podman-remote (container-tools:rhel8) as a component of Red Hat Enterprise Linux 8; podman-tests (container-tools:rhel8) as a component of Red Hat Enterprise Linux 8; podman.src (container-tools:rhel8) as a component of Red Hat Enterprise Linux 8; podman (container-tools:rhel8) as a component of Red Hat Enterprise Linux 8; podman as a component of Red Hat Enterprise Linux 9; podman-catatonit as a component of Red Hat Enterprise Linux 9; podman-docker as a component of Red Hat Enterprise Linux 9; podman-gvproxy as a component of Red Hat Enterprise Linux 9; podman-plugins as a component of Red Hat Enterprise Linux 9; podman-remote as a component of Red Hat Enterprise Linux 9; podman-tests as a component of Red Hat Enterprise Linux 9; podman.src as a component of Red Hat Enterprise Linux 9; openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4; podman as a component of Red Hat OpenShift Container Platform 4; podman-catatonit as a component of Red Hat OpenShift Container Platform 4; podman-docker as a component of Red Hat OpenShift Container Platform 4; podman-gvproxy as a component of Red Hat OpenShift Container Platform 4; podman-manpages as a component of Red Hat OpenShift Container Platform 4; and 7 more · Fixed: podman-main@aarch64 as a component of Red Hat Hardened Images; podman-main@noarch as a component of Red Hat Hardened Images; podman-main@src as a component of Red Hat Hardened Images; podman-main@x86_64 as a component of Red Hat Hardened Images
After
ansible-automation-platform-26/eda-controller-rhel9 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-27/eda-controller-rhel9 as a component of Red Hat Ansible Automation Platform 2; podman as a component of Red Hat Enterprise Linux 10; podman-docker as a component of Red Hat Enterprise Linux 10; podman-remote as a component of Red Hat Enterprise Linux 10; podman-tests as a component of Red Hat Enterprise Linux 10; podman.src as a component of Red Hat Enterprise Linux 10; podman-catatonit (container-tools:rhel8) as a component of Red Hat Enterprise Linux 8; podman-docker (container-tools:rhel8) as a component of Red Hat Enterprise Linux 8; podman-gvproxy (container-tools:rhel8) as a component of Red Hat Enterprise Linux 8; podman-manpages (container-tools:rhel8) as a component of Red Hat Enterprise Linux 8; podman-plugins (container-tools:rhel8) as a component of Red Hat Enterprise Linux 8; podman-remote (container-tools:rhel8) as a component of Red Hat Enterprise Linux 8; podman-tests (container-tools:rhel8) as a component of Red Hat Enterprise Linux 8; podman.src (container-tools:rhel8) as a component of Red Hat Enterprise Linux 8; podman (container-tools:rhel8) as a component of Red Hat Enterprise Linux 8; podman as a component of Red Hat Enterprise Linux 9; podman-catatonit as a component of Red Hat Enterprise Linux 9; podman-docker as a component of Red Hat Enterprise Linux 9; podman-gvproxy as a component of Red Hat Enterprise Linux 9; podman-plugins as a component of Red Hat Enterprise Linux 9; podman-remote as a component of Red Hat Enterprise Linux 9; podman-tests as a component of Red Hat Enterprise Linux 9; podman.src as a component of Red Hat Enterprise Linux 9; openshift/ose-rhel-coreos-8 as a component of Red Hat OpenShift Container Platform 4; openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4; podman as a component of Red Hat OpenShift Container Platform 4; podman-catatonit as a component of Red Hat OpenShift Container Platform 4; podman-docker as a component of Red Hat OpenShift Container Platform 4; podman-gvproxy as a component of Red Hat OpenShift Container Platform 4; and 8 more · Fixed: podman-main@aarch64 as a component of Red Hat Hardened Images; podman-main@noarch as a component of Red Hat Hardened Images; podman-main@src as a component of Red Hat Hardened Images; podman-main@x86_64 as a component of Red Hat Hardened Images
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
