LiveActive security incident?Get immediate response
CVE Record

CVE-2025-4953: Podman: build context bind mount

A flaw was found in Podman. In a Containerfile or Podman, data written to RUN --mount=type=bind mounts during the podman build is not discarded. This issue can lead to files created within the container appearing in the temporary build context directory on the host, leaving the created files accessible.

HighCVSS 7.4Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Podman builds may leave files created inside a build container on the host in a temporary build context. This can expose or alter host-side data during container image builds, especially where teams build untrusted or third-party Containerfiles.

Executive priority

Prioritize remediation for shared build infrastructure and OpenShift/RHEL environments. Business urgency is higher where external code can trigger builds, because the issue crosses the expected container-to-host boundary during image creation.

Technical view

The flaw affects Podman build handling of Containerfile RUN bind mounts. Data written to type=bind mounts is not discarded as expected and can appear in the host temporary build context directory. Red Hat lists affected RHEL container-tools and OpenShift package streams.

Likely exposure

Exposure is most likely in CI/CD, developer workstations, and OpenShift/RHEL environments that run podman or related container build tooling against untrusted Containerfiles or build inputs.

Exploitation context

The bundle does not show CISA KEV listing or active exploitation evidence. CVSS indicates high confidentiality and integrity impact, but high attack complexity. Treat exploitation status as unconfirmed.

Researcher notes

Evidence supports a build-time host artifact exposure flaw, not a runtime container escape. The affected list includes Red Hat platform package streams beyond Podman, so validate exact product advisory coverage before scoping remediation.

Mitigation direction

  • Apply applicable Red Hat errata or vendor updates for affected Podman and container-tools packages.
  • Update affected OpenShift package streams according to the referenced Red Hat advisories.
  • Limit who can submit Containerfiles or build definitions to shared build systems.
  • Run untrusted container builds on isolated, disposable workers where feasible.
  • Check vendor guidance before using manual cleanup as a compensating control.

Validation and detection

  • Inventory Podman, Buildah, container-tools, RHEL, and OpenShift versions against the CVE record.
  • Review CI/CD pipelines for Containerfiles using RUN bind mounts.
  • Confirm relevant Red Hat advisories are applied on build hosts and clusters.
  • Inspect build worker temporary directories for unexpected retained build artifacts.
  • Document whether builds accept untrusted repositories, forks, or third-party Containerfiles.
Prepared
Confidence
medium
Sources
9

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-378: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-4953 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
5Timeline events
1ADP providers
17Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.4CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N2.25.2redhat

Vulnerability scoring details

Base CVSS 3.1 score

7.4High
CVSS 3.1 vector shape for CVE-2025-4953Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. Source timelineredhat

    Reported to Red Hat.

  2. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  3. Source timelineredhat

    Made public.

  4. CVE publishedCVE Program

    The CVE record was published.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Unknown vendorpodmanpodman, 0unknown
Red HatRed Hat Enterprise Linux 8container-tools:rhel8, 8100020250911075811.afee755daffected
Red HatRed Hat OpenShift Container Platform 4.12podman, 3:4.2.0-15.rhaos4.12.el9affected
Red HatRed Hat OpenShift Container Platform 4.12rhcos, 412.86.202601061735-0affected
Red HatRed Hat OpenShift Container Platform 4.13buildah, 1:1.29.1-5.rhaos4.13.el9affected
Red HatRed Hat OpenShift Container Platform 4.13conmon, 3:2.1.7-5.rhaos4.13.el8affected
Red HatRed Hat OpenShift Container Platform 4.13containernetworking-plugins, 1:1.4.0-5.rhaos4.13.el8affected
Red HatRed Hat OpenShift Container Platform 4.13cri-o, 0:1.26.5-26.rhaos4.13.giteb3d487.el8affected
Red HatRed Hat OpenShift Container Platform 4.13cri-tools, 0:1.26.0-7.el8affected
Red HatRed Hat OpenShift Container Platform 4.13haproxy, 0:2.2.24-5.rhaos4.13.el8affected
Red HatRed Hat OpenShift Container Platform 4.13ignition, 0:2.15.0-10.rhaos4.13.el9affected
Red HatRed Hat OpenShift Container Platform 4.13openshift, 0:4.13.0-202410181847.p0.g53fd427.assembly.stream.el8affected
Red HatRed Hat OpenShift Container Platform 4.13openshift4-aws-iso, 0:4.13.0-202410181847.p0.gd2acdd5.assembly.stream.el8affected
Red HatRed Hat OpenShift Container Platform 4.13openshift-ansible, 0:4.13.0-202410181847.p0.g1397e80.assembly.stream.el8affected
Red HatRed Hat OpenShift Container Platform 4.13openshift-clients, 0:4.13.0-202410181847.p0.gd192e90.assembly.stream.el8affected
Red HatRed Hat OpenShift Container Platform 4.13openshift-kuryr, 0:4.13.0-202410181847.p0.g36754b7.assembly.stream.el8affected
Red HatRed Hat OpenShift Container Platform 4.13podman, 3:4.4.1-15.rhaos4.13.el8affected
Red HatRed Hat OpenShift Container Platform 4.13runc, 4:1.1.14-2.rhaos4.13.el8affected
Red HatRed Hat OpenShift Container Platform 4.13skopeo, 2:1.11.3-4.rhaos4.13.el8affected
Red HatRed Hat OpenShift Container Platform 4.13buildah, 1:1.29.5-1.rhaos4.13.el8affected
Red HatRed Hat OpenShift Container Platform 4.13kernel, 0:5.14.0-284.109.1.el9_2affected
Red HatRed Hat OpenShift Container Platform 4.13kernel-rt, 0:5.14.0-284.109.1.rt14.394.el9_2affected
Red HatRed Hat OpenShift Container Platform 4.13podman, 3:4.4.1-16.rhaos4.13.el8affected
Red HatRed Hat OpenShift Container Platform 4.13rhcos, 413.92.202511261311-0affected
Red HatRed Hat OpenShift Container Platform 4.14rhcos, 414.92.202512031525-0affected
Red HatRed Hat OpenShift Container Platform 4.15rhcos, 415.92.202512100122-0affected
Red HatRed Hat OpenShift Container Platform 4.16podman, 4:4.9.4-16.rhaos4.16.el8affected
Red HatRed Hat OpenShift Container Platform 4.16rhcos, 416.94.202512030118-0affected
Red HatRed Hat OpenShift Container Platform 4.17rhcos, 417.94.202511260612-0affected
Red HatRed Hat OpenShift Container Platform 4.18podman, 5:5.2.2-2.rhaos4.18.el8affected
Weakness

CWE details

CWE-378

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-378 · source CWE mapping

Creation of Temporary File With Insecure Permissions

Creation of Temporary File With Insecure Permissions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs