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.

Published: 2025-09-16 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-4953 is rated Low Risk (34.1/100): CVSS High severity, with low exploitation likelihood (EPSS 0.04%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-4953

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-02-12 0.05% 0.04% -0.01%
2 2025-11-11 0.03% 0.05% +0.02%
3 2025-09-17 — 0.03% —

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-4953

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.4 3.1 HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 2.2 5.2 [email protected]

Weakness enumeration for CVE-2025-4953

GitHub Security Advisory for CVE-2025-4953

GHSA-m68q-4hqr-mc6f · Severity: high · Ecosystem: go — Podman Creates Temporary File with Insecure Permissions

OS Trackers for CVE-2025-4953

vendor priority summary link
debian not yet assigned CVE-2025-4953 not yet assigned priority: Debian including 2 source packages (libpod, podman), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 3, open 2. https://security-tracker.debian.org/tracker/CVE-2025-4953
redhat medium — https://access.redhat.com/security/cve/CVE-2025-4953
suse high — https://www.suse.com/security/cve/CVE-2025-4953/
ubuntu medium CVE-2025-4953 medium priority: Ubuntu including 2 source packages (libpod, podman), 10 status rows across 5 suites (jammy, noble, plucky, questing, upstream): needs-triage 5, DNE 4, ignored 1. https://ubuntu.com/security/CVE-2025-4953

Affected software / configurations for CVE-2025-4953

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-4953

cvelogic Threat Intelligence