GHSA-6h2x-4gjf-jc5w — autogluon-multimodal
Fix: awslabs/autogluon#1987GHSA-6h2x-4gjf-jc5w is a remote code execution vulnerability in autogluon-multimodal. A fix is available for autogluon-multimodal — see the affected versions and patch details below.
autogluon.multimodal vulnerable to unsafe YAML deserialization
Real-World Exposure
autogluon-multimodal🐍autogluon-multimodalReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
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.
Patches
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.
Workarounds
Do not load data which originated from an untrusted source, or that could have been tampered with. Only load data you trust.
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | autogluon-multimodal | ≥ 0.4.0&&< 0.4.3 | 0.4.3pip install --upgrade 'autogluon-multimodal==0.4.3' |
| 🐍PyPI | autogluon-multimodal | ≥ 0.5.0&&< 0.5.2 | 0.5.2pip install --upgrade 'autogluon-multimodal==0.5.2' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for autogluon-multimodal, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update autogluon-multimodal to 0.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6h2x-4gjf-jc5w 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 GHSA-6h2x-4gjf-jc5w can be triaged on real exposure rather than presence alone.
Tailored to GHSA-6h2x-4gjf-jc5w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-6h2x-4gjf-jc5w in your dependencies?
O3 Security finds GHSA-6h2x-4gjf-jc5w across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.