CVE-2017-16616: An exploitable vulnerability exists in the YAML parsing functionality in the YAMLParser method in Interfaces.p
CVE-2017-16616 is a critical-severity flaw (CVSS 9.8) affecting pyanyapi. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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.
Why this priority
- Critical severity
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 9.8 (Critical) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 3.6% (top 10%) |
| CISA exploited list | No |
| Published | 2017-11-08 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2017-16616?
pyanyapi: upgrade to 0.6.1. Exact commands for each OS are on this page.
Is CVE-2017-16616 being exploited?
CVE-2017-16616 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2017-16616 affect?
CVE-2017-16616 affects pyanyapi. Severity is critical (CVSS 9.8). 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 use
How urgent is CVE-2017-16616?
Priority 62/100. Critical severity; Remotely exploitable, no login, no user action