No exploitation reportedFix available

CVE-2017-16618

Q: Is CVE-2017-16618 actively exploited?

Active exploitation of CVE-2017-16618 has not been confirmed. Its EPSS score was 4.5% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

Q: What is the CVSS score for CVE-2017-16618?

CVE-2017-16618 has a CVSS v3 base score of 9.8 (CRITICAL severity), with vector string CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

No exploitation reported by the sources we read.

Published2017-11-08
Fixed in2.0.0

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC

2017-11-0803:29CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC

Indicators tagged with this CVE, per day0 indicators over 7 days

Block these indicators

Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2017-16618?format=txt
CSV export: https://api.ismalicious.com/edl/cve/CVE-2017-16618?format=csv
TAXII collection of exploited CVEs
The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD

Owlmixin project owlmixin

Branch	Affected	Fixed in	Source
2.0	< 2.0.0	2.0.0	NVD
2.0	= 2.0.0	no fix published	NVD

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

Update Owlmixin project owlmixin to 2.0.0

Advisories and patches

github.comPatch
github.comPatch

Detection

Nuclei template: none so far
Exploit-DB: no entry
Proof-of-concept repositories: none listed

Sources

NVDCVSS 3.09.8read 2026-10-23
NVDCVSS 2.07.5read 2026-10-23
FIRST EPSSEPSS score4.5 %2026-10-22

Technical details

CVSS v3 Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published: 2017-11-08
Last Modified: 2026-06-17
NVD status: Modified

Frequently asked questions

What is CVE-2017-16618?

Is CVE-2017-16618 actively exploited?

Active exploitation of CVE-2017-16618 has not been confirmed. Its EPSS score was 4.5% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2017-16618?

CVE-2017-16618 has a CVSS v3 base score of 9.8 (CRITICAL severity), with vector string CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this product CISA KEV additions, October 2026 Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database