CVE-2024-9676

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

Score 6.5 from GitHub Security Advisory published 2024-10-15. NVD baseline CVSS 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 1%CVSS: 6.5Exploit: NoneExposed: 0

A fix is available — apply it.

A vulnerability was found in Podman, Buildah, and CRI-O. A symlink traversal vulnerability in the containers/storage library can cause Podman, Buildah, and CRI-O to hang and result in a denial of service via OOM kill when running a malicious image using an automatically assigned user namespace (--userns=auto in Podman and Buildah). The containers/storage library will read /etc/passwd inside the container, but does not properly validate if that file is a symlink, which can be used to cause the library to read an arbitrary file on the host.

CVSS v3
6.5
EG Score
6.5(medium)
EPSS
68.2%
KEV
Not listed

Published

October 15, 2024

Last Modified

March 19, 2026

References (21)

Vendor Advisories for CVE-2024-9676(12)

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

Patch Availability(17)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatopenshift4/ose-docker-builder-rhel9:v4.16.0-202503121138.p0.g31c3c26.assembly.stream.el92025-04-03redhat
redhatopenshift4/ose-docker-builder:v4.14.0-202503060906.p0.gb03f3f5.assembly.stream.el82025-03-19redhat
redhatopenshift4/ose-docker-builder:v4.15.0-202503060734.p0.gbc0b789.assembly.stream.el82025-03-13redhat
redhatopenshift4/ose-docker-builder-rhel9:v4.17.0-202501281204.p0.ga753153.assembly.stream.el92025-02-05redhat
redhatcontainer-tools:rhel8-8100020241101101019.afee755d2024-11-26redhat
redhatbuildah-2:1.33.11-1.el9_42024-11-19redhat
redhatpodman-5:5.2.2-1.rhaos4.17.el82024-11-13redhat
redhatbuildah-2:1.37.5-1.el9_52024-11-12redhat
redhatpodman-4:5.2.2-9.el9_52024-11-12redhat
redhatpodman-4:4.9.4-16.el9_42024-11-11redhat
redhatcri-o-0:1.27.8-12.rhaos4.14.git7597c43.el82024-11-08redhat
redhatcri-o-0:1.25.5-30.rhaos4.12.git53dc492.el82024-11-07redhat
redhatpodman-4:4.9.4-12.rhaos4.16.el82024-11-06redhat
redhatcri-o-0:1.26.5-26.rhaos4.13.giteb3d487.el82024-11-06redhat
redhatcri-o-0:1.28.11-5.rhaos4.15.git35a2431.el82024-10-31redhat
redhatcri-o-0:1.29.9-6.rhaos4.16.gite7bd45a.el82024-10-30redhat
redhatcri-o-0:1.30.6-6.rhaos4.17.git6ac6e96.el82024-10-29redhat

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.

Weakness Classification(1)

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

Additional Vendor Advisories

(6)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 13× in last 7d / 47× 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.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-9676?
CVE-2024-9676 is a medium vulnerability published on October 15, 2024. A vulnerability was found in Podman, Buildah, and CRI-O. A symlink traversal vulnerability in the containers/storage library can cause Podman, Buildah, and CRI-O to hang and result in a denial of service via OOM kill when running a malicious image using an automatically assigned user namespace…
When was CVE-2024-9676 disclosed?
CVE-2024-9676 was first published in the National Vulnerability Database on October 15, 2024, with the most recent update on March 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-9676 actively exploited?
CVE-2024-9676 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 68.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-9676?
CVE-2024-9676 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2024-9676?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-9676, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-9676

Explore →

Is Your Infrastructure Affected by CVE-2024-9676?

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

Start Free Scan →Browse All CVEs