Summary
autogluon.multimodal vulnerable to unsafe YAML deserialization
Workarounds
Do not load data which originated from an untrusted source, or that could have been tampered with. Only load data you trust.
References
Impact
A potential unsafe deserialization issue exists within the autogluon.multimodal module, where YAML files are loaded via yaml.load() instead of yaml.safe_load(). The deserialization of untrusted data may allow an unprivileged third party to cause remote code execution, denial of service, and impact to both confidentiality and integrity.
Impacted versions: >=0.4.0;<0.4.3, >=0.5.0;<0.5.2.
Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect. Typical impact: arbitrary code execution or logic abuse.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
The patches are included in autogluon.multimodal==0.4.3, autogluon.multimodal==0.5.2 and Deep Learning Containers 0.4.3 and 0.5.2.
Frequently Asked Questions
- What is GHSA-6H2X-4GJF-JC5W? GHSA-6H2X-4GJF-JC5W is a high-severity insecure deserialization vulnerability in autogluon.multimodal (pip), affecting versions >= 0.4.0, < 0.4.3. It is fixed in 0.4.3, 0.5.2. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.
- Which versions of autogluon.multimodal are affected by GHSA-6H2X-4GJF-JC5W? autogluon.multimodal (pip) versions >= 0.4.0, < 0.4.3 is affected.
- Is there a fix for GHSA-6H2X-4GJF-JC5W? Yes. GHSA-6H2X-4GJF-JC5W is fixed in 0.4.3, 0.5.2. Upgrade to this version or later.
- Is GHSA-6H2X-4GJF-JC5W exploitable, and should I be worried? Whether GHSA-6H2X-4GJF-JC5W is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-6H2X-4GJF-JC5W is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-6H2X-4GJF-JC5W?
- Upgrade
autogluon.multimodalto 0.4.3 or later - Upgrade
autogluon.multimodalto 0.5.2 or later
- Upgrade