How severe is CVE-2024-3727?

CVE-2024-3727 has a CVSS score of 8.3/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2024-3727?

CVE-2024-3727 affects the following packages: github.com/containers/image (Go), github.com/containers/image/v5 (Go), github.com/containers/image/v5 (Go). Ecosystems affected: Go.

How do I fix CVE-2024-3727?

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

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

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

How do I mitigate CVE-2024-3727 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.

How does O3 Security protect against CVE-2024-3727?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-3727 can be triaged on real exposure rather than presence alone.

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

No public exploit code has been indexed for CVE-2024-3727 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-3727?

CVE-2024-3727 has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 69th 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-3727?

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

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

CVE-2024-3727 was published on May 9, 2024 and was last updated on September 21, 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

HIGH severity

CVE-2024-3727 — image

HIGH

CVE-2024-3727 is a high-severity (CVSS 8.3) CWE-354 vulnerability in github.com/containers/image. A fix is available for github.com/containers/image — see the affected versions and patch details below.

Containers/image: digest type does not guarantee valid type

Also known asGHSA-6wvf-f2vw-3425GO-2024-2842

Published

May 9, 2024

Updated

Sep 21, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Sep 20, 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-3727.

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs69th percentile — riskier than 69% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2024-3727 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

3 pkgs affected

🐹github.com/containers/image🐹github.com/containers/image/v5🐹github.com/containers/image/v5

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 the github.com/containers/image library. This flaw allows attackers to trigger unexpected authenticated registry accesses on behalf of a victim user, causing resource exhaustion, local path traversal, and other attacks.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/containers/image`	all versions	5.30.1`go get github.com/containers/image@v5.30.1`
🐹Go	`github.com/containers/image/v5`	≥ 5.30.0&&< 5.30.1	5.30.1`go get github.com/containers/image/v5@v5.30.1`
🐹Go	`github.com/containers/image/v5`	all versions	5.29.3`go get github.com/containers/image/v5@v5.29.3`

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/image, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/containers/image to 5.30.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-3727 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-3727 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2024-3727. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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

Some conditions are necessary for this attack to occur, such as the attacker being able to upload malicious images to the registry and persuade a victim to pull them. Hence, the severity of this flaw was rated as Moderate.

Product	Fixed in	Advisory
OADP-1.3-RHEL-9	`oadp/oadp-velero-plugin-rhel9:1.3.4-9`	RHSA-2024:9960
Red Hat Advanced Cluster Security 4.4	`advanced-cluster-security/rhacs-central-db-rhel8:4.4.5-2`	RHSA-2024:6054
Red Hat Advanced Cluster Security 4.5	`advanced-cluster-security/rhacs-central-db-rhel8:4.5.2-2`	RHSA-2024:6708
Red Hat Enterprise Linux 8	`container-tools:rhel8-8100020240808093819.afee755d`	RHSA-2024:5258
Red Hat Enterprise Linux 9	`buildah-2:1.37.2-1.el9`	RHSA-2024:9097
Red Hat Enterprise Linux 9	`skopeo-2:1.16.1-1.el9`	RHSA-2024:9098
Red Hat Enterprise Linux 9	`podman-2:5.2.2-1.el9`	RHSA-2024:9102
Red Hat Migration Toolkit for Containers 1.8	`rhmtc/openshift-migration-controller-rhel8:v1.8.4-22`	RHSA-2024:7164

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2024-3727 in your dependencies?

O3 Security finds CVE-2024-3727 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works