Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessPublish malicious checkpoint tarball
-
ExploitVictim loads untrusted checkpoint
-
Executiontarball.extractall follows traversal paths
-
ImpactFiles written outside target directory
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK
2 techniques across 2 tactics: Discovery, Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the victim to load an attacker-controlled or untrusted checkpoint through MosaicML Composer's checkpoint-extraction path, where tarball.extractall processes archive entries without sanitizing paths (CWE-22). The concrete prerequisite is ingestion of a malicious checkpoint tarball (e.g., downloaded from a model hub, shared storage, or supply-chain source) by a deployment running Composer version 0.32.1 or earlier. The primary limiting factor is the required passive user interaction (UI:P): there is no automatic, unauthenticated path unless an environment already loads externally supplied checkpoints; teams that only load their own internally generated, trusted checkpoints are not realistically exposed. |
| Impact | This is a medium-severity (CVSS 4.0 base 5.3) path traversal in MosaicML Composer's checkpoint-extraction logic, and the available signals converge on genuinely moderate - not urgent - risk. The CVSS vector (AV:N/AC:L/AT:N/PR:N/UI:P) indicates no authentication is required but mandates passive user interaction, meaning a victim must actually load an attacker-supplied checkpoint; this is the single most important risk-limiting factor. Impact is rated Low across confidentiality, integrity, and availability with no scope change, so even successful exploitation is bounded rather than catastrophic. No EPSS score was provided in the input, the CVE is NOT on CISA KEV, and no public exploit code (POC) is referenced, so exploitation status is 'no public exploit identified at time of analysis.' There is no conflict between the network attack vector and the description - 'attack can be executed remotely' is consistent with AV:N because the malicious tarball can be delivered over the network, while UI:P correctly reflects that the user must trigger extraction. The key weakness in this assessment is source diversity: the entire record originates from a single researcher/source (VulDB), with no vendor advisory, no NVD CVSS enrichment independent of VulDB, and no confirmed patched version, so confidence in the precise affected-version boundary and impact ratings is limited. Net: treat as a real but lower-priority hardening item for teams that load untrusted/third-party checkpoints, not an emergency. |
| Exploit ScenarioDerived | An attacker publishes a malicious model checkpoint (a crafted tarball) to a public model hub, shared artifact store, or supply-chain channel. A data scientist or ML pipeline using MosaicML Composer <= 0.32.1 loads that checkpoint, and tarball.extractall in composer/utils/checkpoint.py follows '../' entries to write files outside the intended extraction directory, overwriting or planting files on the host. No public POC is referenced, and exploitation requires the victim to initiate the checkpoint load (UI:P). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Path traversal in MosaicML Composer 0.32.1 and earlier allows an attacker who supplies a crafted checkpoint archive to write files outside the intended extraction directory when the victim loads that checkpoint, because the tarball.extractall routine in composer/utils/checkpoint.py does not sanitize archive entry paths (CWE-22). The attack is remote and, per the CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:P), requires only passive user interaction - someone must ingest an untrusted checkpoint, for example one pulled from a model hub, shared storage, or a supply-chain source; the independent assessment corroborates this as CVSS:3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L, i.e., limited integrity and availability impact with no confidentiality loss. No public exploit code was identified and the issue is not in CISA KEV, so this is a medium-severity (base 5.3) supply-chain hygiene problem rather than an actively exploited emergency; teams that only load internally generated, trusted checkpoints are not realistically exposed.
RemediationAI
No vendor-released patch was identified at time of analysis - the vendor was contacted early about the disclosure and the fix is being tracked in upstream issue mosaicml/composer#3942 (https://github.com/mosaicml/composer/issues/3942), with disclosure details at https://vuldb.com/vuln/416887 and https://vuldb.com/cve/CVE-2026-109153, so the first action is to monitor those references for a fixed release and upgrade as soon as one is published. Until then, apply specific compensating controls rather than relying on generic hardening: refuse to extract checkpoints from untrusted or unauthenticated sources (model hubs, public bucket shares, third-party artifact stores) - the trade-off is reduced convenience for pretrained-model workflows, which is acceptable given the supply-chain risk; where extraction of externally sourced archives is unavoidable, pre-screen archives before extraction by listing members and rejecting any entry whose resolved path escapes the target directory (or use Python's tarfile extraction filters such as filter='data' on supported interpreters, or an equivalent safe-extraction wrapper), with the trade-off that legitimate archives using symlinks, hardlinks, or unusual path forms may be rejected or need allowlisting; run checkpoint extraction inside a container or sandbox with the destination directory mounted read-write and every other path read-only, under a low-privilege account, which limits where a traversal write can land but adds operational overhead; and restrict filesystem write permissions on the host so that stray writes cannot reach credential files, shell startup files, or service configuration. Detection should focus on checkpoint archives containing '../' or absolute-path members and on unexpected file creation outside the designated checkpoint directory during load operations.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is MosaicML Composer's checkpoint handling logic in composer/utils/checkpoint.py, which unpacks training-checkpoint tarballs using Python's tarfile.extractall. That API historically performs no validation of member names, so a malicious archive can embed entries containing '../' sequences or absolute paths that escape the destination directory and land anywhere the Composer process can write - the classic CWE-22 improper limitation of a pathname to a restricted directory. The CPE cpe:2.3:a:mosaicml:composer:*:*:*:*:*:*:*:* confirms the affected package is the Composer library itself, and the description scopes impact to versions up to 0.32.1. Because Composer is a machine-learning training framework widely used to load pretrained checkpoints from hubs and shared artifact stores, the tarball-extraction path sits directly on a realistic untrusted-input boundary; the independent assessment stresses that the practical exploitability is gated by the victim actively loading an attacker-controlled or untrusted checkpoint rather than by any automatic, network-reachable code path. The CVSS 4.0 vector's UI:P/AT:N and the assessed 3.1 UI:R both reflect that gating, while PR:N indicates no authentication is required from the attacker who crafts the archive.
Know when Composer gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N
Malicious checkpoint delivered over network but victim must load it (UI:R); arbitrary file write yields limited integrity and availability impact and no confidentiality, so C:N/I:L/A:L.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
DescriptionCVE.org
A vulnerability was detected in MosaicML Composer up to 0.32.1. This affects the function tarball.extractall of the file composer/utils/checkpoint.py of the component Checkpoint Extraction. The manipulation results in path traversal. The attack can be executed remotely. The vendor was contacted early about this disclosure.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
Composer is a dependency manager for PHP. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, lo
Command injection in PHP Composer's Perforce VCS handler allows arbitrary local command execution with the privileges of
The tagDiv Composer WordPress plugin before 4.0 does not sanitise and escape a parameter before outputting it back in th
Composer is an open source dependency manager for the PHP language. Rated critical severity (CVSS 9.8), this vulnerabili
Composer is a dependency manager for PHP. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, lo
Composer is a dependency manager for the PHP programming language. Rated high severity (CVSS 8.8), this vulnerability is
Arbitrary code execution in MosaicML Composer arises when the library loads a model or resumption checkpoint, because ch
Arbitrary file write in Composer (the PHP dependency manager) before 2.2.29 and 2.10.2 allows a malicious package served
The tagDiv Composer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via multiple shortcodes in all ver
Path traversal in Composer's binary installation flow allows a malicious PHP package to cause arbitrary host files to be
Improper input validation in the Drupal Composer contributed module (SA-contrib-2026-046) exposes sites to confidentiali
Credential leakage in Composer PHP dependency manager exposes sensitive tokens - such as GitHub Personal Access Tokens e
EUVD-2026-98450
GHSA-9h32-g52h-pxjh
NVD
CVE.org
EPSS
VulDB
Exploit-DB