CVE-2017-16618: An exploitable vulnerability exists in the YAML loading functionality of util.py in OwlMixin before 2.0.0a12

Q: How do I fix CVE-2017-16618?

owlmixin: upgrade to 2.0.0. Exact commands for each OS are on this page.

Q: Is CVE-2017-16618 being exploited?

CVE-2017-16618 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2017-16618 affect?

CVE-2017-16618 affects owlmixin. Severity is critical (CVSS 9.8). An exploitable vulnerability exists in the YAML loading functionality of util.py in OwlMixin before 2.0.0a12. A "Load YAML" string or file (aka load_yaml or load_yamlf) can execute arbitrary Python commands resulting in command execution be

Q: How urgent is CVE-2017-16618?

Priority 67/100. Critical severity; EPSS top 9%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action

This week

CRITICAL 9.8REMOTEUPGRADE

CVE-2017-16618 is a critical-severity flaw (CVSS 9.8) affecting owlmixin. 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 loading functionality of util.py in OwlMixin before 2.0.0a12. A "Load YAML" string or file (aka load_yaml or load_yamlf) 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
EPSS top 9%: very likely to be exploited
Public exploit reference
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	4.5% (top 9%)
CISA exploited list	No
Published	2017-11-08
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: owlmixin 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

owlmixin project owlmixin UPGRADE

Affected: < 2.0.0 · 2.0.0 alpha1 · 2.0.0 alpha10 · 2.0.0 alpha11 · 2.0.0 alpha2 · 2.0.0 alpha3 · 2.0.0 alpha4 · 2.0.0 alpha5

Fixed in: 2.0.0

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to 2.0.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade owlmixin

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade owlmixin

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

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-16618?

owlmixin: upgrade to 2.0.0. Exact commands for each OS are on this page.

Is CVE-2017-16618 being exploited?

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

CVE-2017-16618 affects owlmixin. Severity is critical (CVSS 9.8). An exploitable vulnerability exists in the YAML loading functionality of util.py in OwlMixin before 2.0.0a12. A "Load YAML" string or file (aka load_yaml or load_yamlf) can execute arbitrary Python commands resulting in command execution be

How urgent is CVE-2017-16618?

Priority 67/100. Critical severity; EPSS top 9%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

Python vulnerabilities

References

← Back to latest CVEs