How severe is CVE-2024-9341?

CVE-2024-9341 has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2024-9341?

CVE-2024-9341 affects the following packages: github.com/containers/common (Go). Ecosystems affected: Go.

How do I fix CVE-2024-9341?

Update github.com/containers/common to 0.60.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-9341 is resolved across your whole dependency graph.

How do I detect CVE-2024-9341 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/containers/common, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-9341 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2024-9341 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-9341 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2024-9341?

CVE-2024-9341 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 64th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-9341?

CVE-2024-9341 is classified as CWE-59 (CWE-59). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-9341 published, and has it been updated?

CVE-2024-9341 was published on October 1, 2024 and was last updated on November 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

MEDIUM severity

CVE-2024-9341 — common

MEDIUMFix: containers/common@e7db065

CVE-2024-9341 is a medium-severity (CVSS 5.4) CWE-59 vulnerability in github.com/containers/common. A fix is available for github.com/containers/common — see the affected versions and patch details below.

Podman: buildah: cri-o: fips crypto-policy directory mounting issue in containers/common go library

Also known asGHSA-mc76-5925-c5p6GO-2024-3171

Published

Oct 1, 2024

Updated

Nov 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-9341.

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs64th percentile — riskier than 64% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐹github.com/containers/common

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

A flaw was found in Go. When FIPS mode is enabled on a system, container runtimes may incorrectly handle certain file paths due to improper validation in the containers/common Go library. This flaw allows an attacker to exploit symbolic links and trick the system into mounting sensitive host directories inside a container. This issue also allows attackers to access critical host files, bypassing the intended isolation between containers and the host system.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/containers/common`	all versions	0.60.4`go get github.com/containers/common@v0.60.4`

Affected Products

3 products · 9 configurations

Application

commoncontainers

all

enterprise linuxredhat

2 versions

8.09.0

Application

openshift container platformredhat

6 versions

4.124.134.144.154.164.17

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/containers/common, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/containers/common to 0.60.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-9341 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for CVE-2024-9341 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat Enterprise Linux 8	`container-tools:rhel8-8100020241023085649.afee755d`	RHSA-2024:8846
Red Hat Enterprise Linux 9	`podman-4:4.9.4-13.el9_4`	RHSA-2024:8039
Red Hat Enterprise Linux 9	`buildah-2:1.33.9-1.el9_4`	RHSA-2024:8112
Red Hat Enterprise Linux 9	`podman-4:5.2.2-9.el9_5`	RHSA-2024:9454
Red Hat Enterprise Linux 9	`buildah-2:1.37.5-1.el9_5`	RHSA-2024:9459
Red Hat OpenShift Container Platform 4.12	`cri-o-0:1.25.5-30.rhaos4.12.git53dc492.el8`	RHSA-2024:8694
Red Hat OpenShift Container Platform 4.13	`cri-o-0:1.26.5-26.rhaos4.13.giteb3d487.el8`	RHSA-2024:8690
Red Hat OpenShift Container Platform 4.14	`cri-o-0:1.27.8-10.rhaos4.14.git807f92c.el8`	RHSA-2024:8238

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2024-9341 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works