CVE-2017-16616

Name: CVE-2017-16616
Creator: NVD / NIST
Published: 2017-11-08T03:29:00.247+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 3.59%

Last modified Jun 17, 2026

CVE-2017-16616 is a vulnerability of currently unknown severity. An exploitable vulnerability exists in the YAML parsing functionality in the YAMLParser method in Interfaces.py in PyAnyAPI before 0.6.1. A YAML parser can execute arbitrary Python commands resulting in command execution because load is used where safe_load should have been used. EPSS estimates a 3.59% chance of exploitation in the next 30 days.

Description

An exploitable vulnerability exists in the YAML parsing functionality in the YAMLParser method in Interfaces.py in PyAnyAPI before 0.6.1. A YAML parser can execute arbitrary Python commands resulting in command execution because load is used where safe_load should have been used. An attacker can insert Python into loaded YAML to trigger this vulnerability.

Metrics

EPSS Probability

3.59%

88.0th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Vendor	Product	Versions
Pyanyapi Project	Pyanyapi	< 0.6.1

References

https://github.com/Stranger6667/pyanyapi/issues/41Issue Tracking
https://github.com/Stranger6667/pyanyapi/releases/tag/0.6.1Release Notes
https://joel-malwarebenchmark.github.io/blog/2017/11/08/cve-2017-16616-yamlparser-in-pyanyapi/Third Party Advisory
https://pypi.python.org/pypi/pyanyapi/0.6.1Product
https://github.com/Stranger6667/pyanyapi/issues/41Issue Tracking
https://github.com/Stranger6667/pyanyapi/releases/tag/0.6.1Release Notes
https://joel-malwarebenchmark.github.io/blog/2017/11/08/cve-2017-16616-yamlparser-in-pyanyapi/Third Party Advisory
https://pypi.python.org/pypi/pyanyapi/0.6.1Product

Timeline

Published: Nov 8, 2017
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2017-16616?

How severe is CVE-2017-16616?

Severity scoring for CVE-2017-16616 is pending analysis. The EPSS model estimates a 3.59% probability of exploitation in the next 30 days.

How do I fix CVE-2017-16616?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-16616?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST