VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

confire: vulnerability history, versions and safety

confire is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 3 releases, from Nov 2017 to Jul 2018. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded C1 U1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all confire vulnerabilities

Vulert verdict on confire 0.2.0 i

Updated on 23 Oct 2026

Careful: 0.2.0 has 2 known vulnerabilities, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 42/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Little adoption
  • Community Inactive

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 0.2.0 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 18 Jul 2018 i
  • Highest CVSS 9.8 i
  • With no published fix 1 i
  • Depended on by 1 packages i
  • Stars 36 i
  • OpenSSF scorecard 1/10 i
  • Last release 146 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for confire, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
0.2.0 01 Aug 2014 C1 U1 MIT No Details →
0.1.1 24 Jul 2014 C1 U1 MIT No Details →
0.1.0 20 Jul 2014 C1 U1 MIT No Details →

All 3 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 1
  • 2018 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for confire

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-16763: confire - Arbitrary Command Execution 9.8 critical No fix published 18 Jul 2018
CVE-2017-16763: YAML Parsing Arbitrary Command Execution in Confire N/A unrated 8cc86a5ec2327e070f1d576d61bbaadf861597ea 10 Nov 2017

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About confire

Is confire safe to use?

Vulert records 2 vulnerabilities for confire in PyPI: 1 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is confire's Vulert package health score?

Vulert scores confire 42/100, which reads as risky. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of confire affected?

Yes. 0.2.0, the version you would install today, has 2 known vulnerabilities, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does confire have?

2 vulnerabilities are recorded for confire in the PyPI ecosystem: 1 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new confire vulnerabilities disclosed?

0 vulnerabilities were recorded for confire in the last 12 months, and the oldest entry in this database dates to 10 Nov 2017. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of confire are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor confire for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the confire version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.