Deserialization of Untrusted Data in parlaiGHSA-m87f-9fvv-2mgg
HIGHFix: facebookresearch/ParlAI@4374fa2GHSA-m87f-9fvv-2mgg is a high-severity (CVSS 8.4) Deserialization of Untrusted Data vulnerability in parlai. 2 public exploit references exist, so weaponization risk is real. A fix is available for parlai — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-m87f-9fvv-2mgg by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,987 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
parlaiReal-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
Due to use of unsafe YAML deserialization logic, an attacker with the ability to modify local YAML configuration files could provide malicious input, resulting in remote code execution or similar risks.
Patches
The issue can be patched by upgrading to v1.1.0 or later. It can also be patched by replacing YAML deserialization with equivalent safe_load calls.
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | parlai | all versions | 1.1.0pip install --upgrade 'parlai==1.1.0' |
Affected Products
parlaifacebookResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Facebook ParlAI 1.0.0 - Deserialization of Untrusted Data in parlai
by Abhiram V · Sep 13, 2021
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for parlai, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update parlai to 1.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m87f-9fvv-2mgg is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.
Frequently Asked Questions
Is GHSA-m87f-9fvv-2mgg in your dependencies?
Find it across PyPI, including transitive dependencies.