CVE-2017-16763: An exploitable vulnerability exists in the YAML parsing functionality in config.py in Confire 0.2.0

This week

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2017-16763 is a critical-severity flaw (CVSS 9.8) affecting confire. 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 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.

Why this priority

Critical severity
EPSS top 9%: very likely to be exploited
Public exploit reference
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	4.5% (top 9%)
CISA exploited list	No
Published	2017-11-10
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: confire 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-10 09:29 UTCPublished CVE record published
2026-06-17 01:09 UTCUpdated Record last modified

confire project confire DOWNGRADE

Affected: 0.2.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.2.0

1. Check installed version

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

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

apt-cache madison confire sudo apt install confire=<VERSION_BEFORE_0.2.0> sudo apt-mark hold confire

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

dnf --showduplicates list confire sudo dnf downgrade confire-<VERSION_BEFORE_0.2.0> sudo dnf versionlock add confire

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

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

Is CVE-2017-16763 being exploited?

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

CVE-2017-16763 affects confire. Severity is critical (CVSS 9.8). 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 arbitrar

How urgent is CVE-2017-16763?

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