CVE-2026-84202
Unsafe YAML deserialization in ModelScope allows remote code execution via malicious model configs
Is CVE-2026-84202 being exploited?
Not confirmed. CVE-2026-84202 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.37% probability of exploitation in the next 30 days.
How severe is CVE-2026-84202?
CVE-2026-84202 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-84202?
Yes. A fix has been recorded for CVE-2026-84202. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-84202 affect?
CVE-2026-84202 affects ModelScope <= 1.40.0, Projects loading untrusted model repositories, Python environments using ModelScope. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-84202?
Upgrade ModelScope to patched release; avoid loading untrusted model repos; use safe YAML parsing.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Arbitrary code execution when loading attacker-controlled YAML model configs, enabling supply-chain RCE and system compromise.
Immediate action required
- affected<= 1.40.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.