CVE-2017-16763

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2018-07-18. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 4%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An exploitable vulnerability exists in the YAML parsing functionality in config.py in Confire 0.2.0. Due to the user-specific configuration being loaded from "~/.confire.yaml" using the yaml.load function, a YAML parser can execute arbitrary Python commands resulting in command execution. An attacker can insert Python into loaded YAML to trigger this vulnerability.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
90.2%
KEV
Not listed

Published

November 10, 2017

Last Modified

May 13, 2026

Advisory Details (3)

Auto-updated May 15, 2026
No patch confirmed yet.
generic

CVE-2017-16763: configure loaded through Confire - Joel

https://joel-malwarebenchmark.github.io/blog/2017/11/12/cve-2017-16763-configure-loaded-through-confire/
generic

load() method in class Configuration is vulnerable · Issue #24 · bbengfort/confire · GitHub

https://github.com/bbengfort/confire/issues/24
generic

use safe load instead of load · bbengfort/confire@8cc86a5 · GitHub

https://github.com/bbengfort/confire/commit/8cc86a5ec2327e070f1d576d61bbaadf861597ea

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
pipconfire—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
confire0.1.0, 0.1.1, 0.2.08cc86a5ec2327e070f1d576d61bbaadf861597ea—

Data Freshness Timeline

(refreshed 9× in last 7d / 39× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 13:42 UTCEPSS rescore
  2. 2026-07-06 16:24 UTCEPSS rescore
  3. 2026-07-06 02:20 UTCEPSS rescore
  4. 2026-07-05 02:27 UTCEPSS rescore
  5. 2026-07-04 06:28 UTCEPSS rescore
  6. 2026-07-01 15:02 UTCEPSS rescore
  7. 2026-07-01 15:02 UTCEPSS rescore
  8. 2026-06-30 23:19 UTCEPSS rescore
  9. 2026-06-30 23:19 UTCEPSS rescore
  10. 2026-06-29 14:03 UTCEPSS rescore
  11. 2026-06-28 14:04 UTCEPSS rescore
  12. 2026-06-28 04:53 UTCEPSS rescore
  13. 2026-06-27 03:05 UTCEPSS rescore
  14. 2026-06-25 13:47 UTCEPSS rescore
  15. 2026-06-25 13:47 UTCEPSS rescore
  16. 2026-06-24 14:02 UTCEPSS rescore
  17. 2026-06-23 21:30 UTCEPSS rescore
  18. 2026-06-22 14:23 UTCEPSS rescore
  19. 2026-06-22 14:23 UTCEPSS rescore
  20. 2026-06-21 14:54 UTCEPSS rescore
  21. 2026-06-21 14:54 UTCEPSS rescore
  22. 2026-06-21 01:57 UTCEPSS rescore
  23. 2026-06-21 01:57 UTCEPSS rescore
  24. 2026-06-19 19:23 UTCEPSS rescore
  25. 2026-06-19 19:23 UTCEPSS rescore
Show 61 more
  1. 2026-06-19 07:25 UTCOSV refresh
  2. 2026-06-18 17:50 UTCEPSS rescore
  3. 2026-06-17 17:50 UTCEPSS rescore
  4. 2026-06-16 17:50 UTCEPSS rescore
  5. 2026-06-15 17:45 UTCEPSS rescore
  6. 2026-06-14 23:14 UTCEPSS rescore
  7. 2026-06-14 23:14 UTCEPSS rescore
  8. 2026-06-13 22:57 UTCEPSS rescore
  9. 2026-06-12 23:09 UTCEPSS rescore
  10. 2026-06-11 13:57 UTCEPSS rescore
  11. 2026-06-10 22:15 UTCEPSS rescore
  12. 2026-06-08 14:14 UTCEPSS rescore
  13. 2026-06-07 15:22 UTCEPSS rescore
  14. 2026-06-07 15:22 UTCEPSS rescore
  15. 2026-06-05 22:44 UTCEPSS rescore
  16. 2026-06-05 06:08 UTCEPSS rescore
  17. 2026-06-05 06:08 UTCEPSS rescore
  18. 2026-06-04 13:10 UTCEPSS rescore
  19. 2026-06-04 13:10 UTCEPSS rescore
  20. 2026-06-02 20:11 UTCEPSS rescore
  21. 2026-06-02 20:11 UTCEPSS rescore
  22. 2026-06-01 13:49 UTCEPSS rescore
  23. 2026-06-01 13:49 UTCEPSS rescore
  24. 2026-05-31 22:28 UTCEPSS rescore
  25. 2026-05-31 00:14 UTCEPSS rescore
  26. 2026-05-30 17:53 UTCOSV refresh
  27. 2026-05-29 13:41 UTCEPSS rescore
  28. 2026-05-28 13:42 UTCEPSS rescore
  29. 2026-05-28 13:42 UTCEPSS rescore
  30. 2026-05-27 13:38 UTCEPSS rescore
  31. 2026-05-27 13:38 UTCEPSS rescore
  32. 2026-05-26 13:42 UTCEPSS rescore
  33. 2026-05-26 13:42 UTCEPSS rescore
  34. 2026-05-26 07:17 UTCEPSS rescore
  35. 2026-05-26 07:17 UTCEPSS rescore
  36. 2026-05-22 21:15 UTCEPSS rescore
  37. 2026-05-22 21:15 UTCEPSS rescore
  38. 2026-05-22 21:15 UTCEPSS rescore
  39. 2026-05-20 22:37 UTCEPSS rescore
  40. 2026-05-20 22:37 UTCEPSS rescore
  41. 2026-05-20 11:21 UTCEPSS rescore
  42. 2026-05-20 11:21 UTCEPSS rescore
  43. 2026-05-20 07:27 UTCEG score recompute
  44. 2026-05-20 07:27 UTCGHSA enrichment
  45. 2026-05-20 03:31 UTCEG score recompute
  46. 2026-05-20 03:31 UTCGHSA enrichment
  47. 2026-05-19 23:35 UTCEG score recompute
  48. 2026-05-19 23:35 UTCGHSA enrichment
  49. 2026-05-19 19:39 UTCEG score recompute
  50. 2026-05-19 19:39 UTCGHSA enrichment
  51. 2026-05-19 15:43 UTCEG score recompute
  52. 2026-05-19 15:43 UTCGHSA enrichment
  53. 2026-05-19 11:47 UTCEG score recompute
  54. 2026-05-19 11:47 UTCGHSA enrichment
  55. 2026-05-19 07:19 UTCEG score recompute
  56. 2026-05-19 07:19 UTCGHSA enrichment
  57. 2026-05-19 03:24 UTCEG score recompute
  58. 2026-05-19 03:23 UTCGHSA enrichment
  59. 2026-05-18 23:27 UTCEG score recompute
  60. 2026-05-18 21:30 UTCEPSS rescore
  61. 2026-05-18 21:30 UTCEPSS rescore

Frequently asked(5)

What is CVE-2017-16763?
CVE-2017-16763 is a critical vulnerability published on November 10, 2017. An exploitable vulnerability exists in the YAML parsing functionality in config.py in Confire 0.2.0. Due to the user-specific configuration being loaded from "~/.confire.yaml" using the yaml.load function, a YAML parser can execute arbitrary Python commands resulting in command execution. An…
When was CVE-2017-16763 disclosed?
CVE-2017-16763 was first published in the National Vulnerability Database on November 10, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-16763 actively exploited?
CVE-2017-16763 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 90.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-16763?
CVE-2017-16763 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-16763?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-16763, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-16763

Explore →

Is Your Infrastructure Affected by CVE-2017-16763?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs