CVE-2017-16615: An exploitable vulnerability exists in the YAML parsing functionality in the parse_yaml_query method in parser

This week

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2017-16615 is a critical-severity flaw (CVSS 9.8) affecting mlalchemy. 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 parse_yaml_query method in parser.py in MLAlchemy before 0.2.2. When processing YAML-Based queries for data, 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

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	3.4% (top 11%)
CISA exploited list	No
Published	2017-11-08
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: mlalchemy project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2017-11-08 03:29 UTCPublished CVE record published
2026-06-17 01:09 UTCUpdated Record last modified

mlalchemy project mlalchemy DOWNGRADE

Affected: 0.1.1 · 0.1.2 · 0.1.3 · 0.2.0 · 0.2.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.1.1

1. Check installed version

apt-cache policy mlalchemy || rpm -q mlalchemy || mlalchemy --version

2. No fixed release: DOWNGRADE to a release before 0.1.1 (Debian / Ubuntu)

apt-cache madison mlalchemy sudo apt install mlalchemy=<VERSION_BEFORE_0.1.1> sudo apt-mark hold mlalchemy

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list mlalchemy sudo dnf downgrade mlalchemy-<VERSION_BEFORE_0.1.1> sudo dnf versionlock add mlalchemy

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
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-16615?

mlalchemy: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2017-16615 being exploited?

CVE-2017-16615 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-16615 affect?

CVE-2017-16615 affects mlalchemy. Severity is critical (CVSS 9.8). An exploitable vulnerability exists in the YAML parsing functionality in the parse_yaml_query method in parser.py in MLAlchemy before 0.2.2. When processing YAML-Based queries for data, a YAML parser can execute arbitrary Python commands re

How urgent is CVE-2017-16615?

Priority 62/100. Critical severity; Remotely exploitable, no login, no user action

Software pages

Python vulnerabilities

References

← Back to latest CVEs