Approved changes feed: RSS · Atom
cpe:2.3:a:pyyaml:pyyaml:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Pyyaml (5d34acb3-0d0f-5f7a-b9a5-555c650c6d60) |
|---|---|
| Product | Pyyaml (c792a206-ada8-5415-8862-b8b7fc4c7c69) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:deb/debian/pyyaml |
purl2cpe | 2026-06-01 10:12:38.283878 |
pkg:deb/ubuntu/pyyaml |
purl2cpe | 2026-06-01 10:12:38.283880 |
pkg:github/yaml/pyyaml |
purl2cpe | 2026-06-01 10:12:38.283881 |
pkg:gitlab/redhat/pyyaml |
purl2cpe | 2026-06-01 10:12:38.283883 |
pkg:pypi/pyyaml |
purl2cpe | 2026-06-01 10:12:38.283884 |
pkg:rpm/centos/pyyaml |
purl2cpe | 2026-06-01 10:12:38.283886 |
pkg:rpm/fedora/pyyaml |
purl2cpe | 2026-06-01 10:12:38.283887 |
pkg:rpm/opensuse/pyyaml |
purl2cpe | 2026-06-01 10:12:38.283888 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2020-1747 |
vulnerable | 2026-06-08 05:21:02.952584 |
Details available
CRITICAL (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 vulnerable to this flaw. An attacker could use this flaw to execute arbitrary code on the system by abusing the python/object/new constructor.
Published: 2020-03-24T13:56:37.000Z
Updated: 2024-08-04T06:46:30.893Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-14343 |
vulnerable | 2026-06-08 05:19:23.060616 |
Details available
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 vulnerable to this flaw. This flaw allows an attacker to execute arbitrary code on the system by abusing the python/object/new constructor. This flaw is due to an incomplete fix for CVE-2020-1747.
Published: 2021-02-09T00:00:00.000Z
Updated: 2024-08-04T12:39:36.530Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2019-20477 |
vulnerable | 2026-06-08 05:13:40.678084 |
Details available
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.
Published: 2020-02-19T03:09:21.000Z
Updated: 2024-08-05T02:39:10.138Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2017-18342 |
vulnerable | 2026-06-08 05:09:10.960767 |
Details available
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.
Published: 2018-06-27T12:00:00.000Z
Updated: 2024-08-05T21:20:50.850Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.