CVE-2024-36623

moby through v25.0.3 has a Race Condition vulnerability in the streamformatter package which can be used to trigger multiple concurrent write operations resulting in data corruption or application crashes.

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-36623 is rated Moderate Risk (48.8/100): CVSS High severity, with low exploitation likelihood (EPSS 0.63%). Review affected assets and schedule remediation.

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-36623

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-06-15 0.05% 0.63% +0.57%
2 2026-01-07 0.27% 0.05% -0.22%
3 2025-11-21 — 0.27% —

Full EPSS history (10 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.1 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.2 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2024-36623

GitHub Security Advisory for CVE-2024-36623

OS Trackers for CVE-2024-36623

vendor priority summary link
debian not yet assigned CVE-2024-36623 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-36623
redhat high — https://access.redhat.com/security/cve/CVE-2024-36623
suse high CVE-2024-36623 severity important: 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-36623/
ubuntu medium CVE-2024-36623 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 9, ignored 3, not-affected 3, needs-triage 1. https://ubuntu.com/security/CVE-2024-36623

Affected software / configurations for CVE-2024-36623

Vendor Product Version Raw CPE
mobyproject moby <= 25.0.3 cpe:2.3:a:mobyproject:moby:*:*:*:*:*:*:*:*

References for CVE-2024-36623

cvelogic Threat Intelligence