CVE-2025-4953

HIGHPre-NVD 7.47.4—
EchelonGraph scoreMEDIUM confidence

Score 7.4 from GitHub Security Advisory (severity: HIGH) published 2025-09-16. a secondary CVSS source baseline 7.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
7.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.4
EG Score
7.4HIGHmedium confidence
EG Risk
34
EG Risk 34/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity74% × 45%
Exploitation1% × 40%
Automatability0% × 15%
EPSS PROB
0.6%
EPSS %ILE
49th
KEV
Not listed

Published

September 16, 2025

Last Modified

September 1, 2026

Advisory Details (10)

Auto-updated Jun 25, 2026
Patch available. Sources: redhat.
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2025:22732
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2025:22724
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2025:22695
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2025:22275
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2025:22265
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2025:17669
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2025:16729
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2025:16724
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 8.

https://access.redhat.com/errata/RHSA-2025:15904
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2024:8690

Vendor Advisories for CVE-2025-4953(14)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(14)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhcos-412.86.202601061735-02026-01-15redhat
redhatrhcos-415.92.202512100122-02026-01-07redhat
redhatrhcos-418.94.202512022246-02025-12-11redhat
redhatrhcos-414.92.202512031525-02025-12-11redhat
redhatrhcos-416.94.202512030118-02025-12-10redhat
redhatrhcos-413.92.202511261311-02025-12-05redhat
redhatrhcos-417.94.202511260612-02025-12-03redhat
redhatpodman-3:4.2.0-15.rhaos4.12.el92025-10-16redhat
redhatpodman-5:5.2.2-2.rhaos4.18.el82025-10-01redhat
redhatpodman-4:4.9.4-16.rhaos4.16.el82025-10-01redhat
redhatcontainer-tools:rhel8-8100020250911075811.afee755d2025-09-16redhat
redhatpodman-3:4.4.1-16.rhaos4.13.el82025-03-20redhat
redhatskopeo-2:1.11.3-4.rhaos4.13.el82024-11-06redhat
gogithub.com/containers/podman/v5—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(9 across 5 ecosystems)
Go(5)
PackageVulnerable rangeFix by version rangeDependents
github.com/containers/podman—
  • every version on: no fix on record
—
github.com/containers/podman/v2—
  • every version on: no fix on record
—
github.com/containers/podman/v3—
  • every version on: no fix on record
—
github.com/containers/podman/v4—
  • every version on: no fix on record
—
github.com/containers/podman/v5—
  • every version through 5.5.0: no fix on record
  • every version on: no fix on record
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
libpod3.0.1+dfsg1-3 ... 5.2.2+ds1-2 (91 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libpod4.3.1+ds1-8 ... 5.2.2+ds1-2 (46 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
podman—
  • every version up to 5.3.2+ds1-1: fixed in 5.3.2+ds1-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
podman—
  • every version up to 5.3.2+ds1-1: fixed in 5.3.2+ds1-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 230 total refreshes for this CVE.

  1. 2026-10-10 00:55 UTCOSV refresh
  2. 2026-10-09 20:06 UTCEPSS rescore
  3. 2026-10-08 17:10 UTCEPSS rescore
  4. 2026-10-07 23:47 UTCEPSS rescore
  5. 2026-10-06 15:17 UTCEPSS rescore
  6. 2026-10-05 17:42 UTCEPSS rescore
  7. 2026-10-04 23:21 UTCEPSS rescore
  8. 2026-10-03 14:24 UTCEPSS rescore
  9. 2026-10-01 19:49 UTCEPSS rescore
  10. 2026-09-30 15:02 UTCEPSS rescore
  11. 2026-09-30 15:02 UTCEPSS rescore
  12. 2026-09-28 13:50 UTCEPSS rescore
  13. 2026-09-27 13:45 UTCEPSS rescore
  14. 2026-09-26 15:58 UTCEPSS rescore
  15. 2026-09-26 00:25 UTCEPSS rescore
  16. 2026-09-24 14:02 UTCEPSS rescore
  17. 2026-09-24 14:02 UTCEPSS rescore
  18. 2026-09-23 13:47 UTCEPSS rescore
  19. 2026-09-21 21:06 UTCEPSS rescore
  20. 2026-09-20 20:15 UTCEPSS rescore
  21. 2026-09-20 20:15 UTCEPSS rescore
  22. 2026-09-20 09:03 UTCOSV refresh
  23. 2026-09-18 19:27 UTCEPSS rescore
  24. 2026-09-18 19:27 UTCEPSS rescore
  25. 2026-09-17 19:29 UTCEPSS rescore
Show 75 more
  1. 2026-09-16 14:07 UTCEPSS rescore
  2. 2026-09-15 03:09 UTCEPSS rescore
  3. 2026-09-12 15:00 UTCEPSS rescore
  4. 2026-09-11 14:52 UTCEPSS rescore
  5. 2026-09-11 09:36 UTCEPSS rescore
  6. 2026-09-10 09:34 UTCEPSS rescore
  7. 2026-09-08 21:59 UTCEPSS rescore
  8. 2026-09-07 16:00 UTCEPSS rescore
  9. 2026-09-07 16:00 UTCEPSS rescore
  10. 2026-09-06 13:46 UTCEPSS rescore
  11. 2026-09-05 15:28 UTCEPSS rescore
  12. 2026-09-04 05:06 UTCEPSS rescore
  13. 2026-09-02 14:11 UTCEPSS rescore
  14. 2026-09-01 13:53 UTCEPSS rescore
  15. 2026-09-01 12:30 UTCEG score recompute
  16. 2026-09-01 12:30 UTCVendor advisory
  17. 2026-09-01 12:30 UTCGHSA enrichment
  18. 2026-09-01 11:57 UTCEG score recompute
  19. 2026-09-01 11:57 UTCVendor advisory
  20. 2026-09-01 11:57 UTCGHSA enrichment
  21. 2026-09-01 04:38 UTCEPSS rescore
  22. 2026-08-31 18:36 UTCEG score recompute
  23. 2026-08-31 18:36 UTCVendor advisory
  24. 2026-08-31 18:36 UTCGHSA enrichment
  25. 2026-08-31 17:27 UTCEG score recompute
  26. 2026-08-31 17:27 UTCVendor advisory
  27. 2026-08-31 17:26 UTCGHSA enrichment
  28. 2026-08-30 19:16 UTCEPSS rescore
  29. 2026-08-30 01:21 UTCEPSS rescore
  30. 2026-08-28 21:40 UTCEPSS rescore
  31. 2026-08-27 14:24 UTCEPSS rescore
  32. 2026-08-26 14:45 UTCEPSS rescore
  33. 2026-08-25 13:48 UTCEPSS rescore
  34. 2026-08-24 14:16 UTCEPSS rescore
  35. 2026-08-24 09:22 UTCEPSS rescore
  36. 2026-08-23 00:18 UTCEPSS rescore
  37. 2026-08-21 23:48 UTCEPSS rescore
  38. 2026-08-21 13:23 UTCEG score recompute
  39. 2026-08-21 13:23 UTCVendor advisory
  40. 2026-08-21 13:23 UTCGHSA enrichment
  41. 2026-08-21 12:50 UTCEG score recompute
  42. 2026-08-21 12:50 UTCVendor advisory
  43. 2026-08-21 12:50 UTCGHSA enrichment
  44. 2026-08-20 22:54 UTCEPSS rescore
  45. 2026-08-19 17:03 UTCEPSS rescore
  46. 2026-08-18 13:47 UTCEPSS rescore
  47. 2026-08-17 13:46 UTCEPSS rescore
  48. 2026-08-16 14:55 UTCEPSS rescore
  49. 2026-08-16 02:13 UTCEPSS rescore
  50. 2026-08-15 01:29 UTCEPSS rescore
  51. 2026-08-13 21:59 UTCEPSS rescore
  52. 2026-08-12 13:50 UTCEPSS rescore
  53. 2026-08-12 05:47 UTCOSV refresh
  54. 2026-08-11 13:41 UTCEPSS rescore
  55. 2026-08-10 23:59 UTCEPSS rescore
  56. 2026-08-09 13:46 UTCEPSS rescore
  57. 2026-08-08 16:36 UTCEPSS rescore
  58. 2026-08-06 13:46 UTCEPSS rescore
  59. 2026-08-05 19:16 UTCEPSS rescore
  60. 2026-08-04 15:09 UTCEPSS rescore
  61. 2026-08-04 10:37 UTCEPSS rescore
  62. 2026-08-03 10:35 UTCEPSS rescore
  63. 2026-08-02 02:26 UTCEPSS rescore
  64. 2026-08-01 04:15 UTCEPSS rescore
  65. 2026-07-30 16:27 UTCEPSS rescore
  66. 2026-07-30 01:30 UTCEPSS rescore
  67. 2026-07-30 01:30 UTCEPSS rescore
  68. 2026-07-28 15:35 UTCEPSS rescore
  69. 2026-07-27 11:39 UTCOSV refresh
  70. 2026-07-26 14:54 UTCEPSS rescore
  71. 2026-07-25 14:17 UTCEPSS rescore
  72. 2026-07-25 14:17 UTCEPSS rescore
  73. 2026-07-24 14:17 UTCEPSS rescore
  74. 2026-07-23 14:18 UTCEPSS rescore
  75. 2026-07-23 02:57 UTCEG score recompute

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-4953?
CVE-2025-4953 is a high vulnerability published on September 16, 2025. 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…
When was CVE-2025-4953 disclosed?
CVE-2025-4953 was first published on September 16, 2025, with the most recent update on September 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-4953 actively exploited?
CVE-2025-4953 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-4953?
CVE-2025-4953 has a CVSS base score of 7.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-4953?
A fix for CVE-2025-4953 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-4953 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-4953

Explore →

Is Your Infrastructure Affected by CVE-2025-4953?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs