CVE-2024-36621

moby v25.0.5 is affected by a Race Condition in builder/builder-next/adapters/snapshot/layer.go. The vulnerability could be used to trigger concurrent builds that call the EnsureLayer function resulting in resource leaks/exhaustion.

Published: 2024-11-29 Last update: 2025-07-02 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-36621 is rated Low Risk (32.7/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.06%). 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-2024-36621

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-01-07 0.22% 0.06% -0.16%
2 2025-11-21 0.30% 0.22% -0.08%
3 2025-11-18 — 0.30% —

Full EPSS history (10 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-36621

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H 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:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
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:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2024-36621

GitHub Security Advisory for CVE-2024-36621

OS Trackers for CVE-2024-36621

vendor priority summary link
debian not yet assigned CVE-2024-36621 not yet assigned priority: Debian including 1 source packages (docker.io), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 3, open 2. https://security-tracker.debian.org/tracker/CVE-2024-36621
redhat medium — https://access.redhat.com/security/cve/CVE-2024-36621
suse medium CVE-2024-36621 severity moderate: SUSE including 11 source package names (docker, docker-bash-completion, …), 107 product×package rows across 51 product lines (Container suse/sl-micro/6.0/baremetal-os-container, Container suse/sl-micro/6.0/toolbox, … (51 product lines)): Known Not Affected 81, Fixed 26. https://www.suse.com/security/cve/CVE-2024-36621/
ubuntu medium CVE-2024-36621 medium priority: Ubuntu including 2 source packages (docker.io, docker.io-app), 16 status rows across 9 suites (bionic, focal, jammy, noble, oracular, plucky, questing, upstream, xenial): released 7, needs-triage 4, ignored 3, not-affected 2. https://ubuntu.com/security/CVE-2024-36621

Affected software / configurations for CVE-2024-36621

Vendor Product Version Raw CPE
mobyproject moby 25.0.5 cpe:2.3:a:mobyproject:moby:25.0.5:*:*:*:*:*:*:*

References for CVE-2024-36621

cvelogic Threat Intelligence