https://patchthecve.com/CVEs with upgrade or downgrade fix stepshttps://patchthecve.com/cve/CVE-2020-14343.htmlhttps://patchthecve.com/cve/CVE-2020-14343.htmlWed, 17 Jun 2026 02:54:34 +0000CRITICAL 9.8: A vulnerability was discovered in the PyYAML library in versions before 5.4, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnhttps://patchthecve.com/cve/CVE-2020-1747.htmlhttps://patchthecve.com/cve/CVE-2020-1747.htmlWed, 17 Jun 2026 03:02:19 +0000CRITICAL 9.8: A vulnerability was discovered in the PyYAML library in versions before 5.3.1, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vuhttps://patchthecve.com/cve/CVE-2019-20477.htmlhttps://patchthecve.com/cve/CVE-2019-20477.htmlWed, 17 Jun 2026 02:30:32 +0000CRITICAL 9.8: PyYAML 5.1 through 5.1.2 has insufficient restrictions on the load and load_all functions because of a class deserialization issue, e.g., Popen is a class in the subprocess module. NOTE: this issue exists because of an incomplete fix for CVE-2017-18342.https://patchthecve.com/cve/CVE-2017-18342.htmlhttps://patchthecve.com/cve/CVE-2017-18342.htmlWed, 17 Jun 2026 01:12:39 +0000CRITICAL 9.8: In PyYAML before 5.1, the yaml.load() API could execute arbitrary code if used with untrusted data. The load() function has been deprecated in version 5.1 and the 'UnsafeLoader' has been introduced for backward compatibility with the function.