VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

smart_proxy_dynflow: vulnerability history, versions and safety

smart_proxy_dynflow is a package in the RubyGems ecosystem. Vulert records 1 vulnerability for it across 1 release, first recorded in Oct 2018. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded C1
i
0 with no fix published

Every vulnerability has a patched version to move to.

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 smart_proxy_dynflow vulnerabilities

Vulert verdict on smart_proxy_dynflow 1.0.0 i

Updated on 23 Oct 2026

Good news: 1.0.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 87/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Not enough data
  • Community Not enough data

What to do: Stay on 1.0.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 1.0.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 1.0.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 08 Oct 2018 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Last release 9 months ago i
  • Licence GPL-3.0-only i

Version list, release dates, licence and dependants published by RubyGems, 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 smart_proxy_dynflow, 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
1.0.0 05 Jan 2026 none GPL-3.0-only — Details →
0.9.4 20 Nov 2024 none GPL-3.0-only — Details →
0.9.3 14 Aug 2024 none GPL-3.0 — Details →
0.9.2 05 Mar 2024 none GPL-3.0 — Details →
0.9.1 20 Oct 2023 none GPL-3.0 — Details →
0.9.0 11 Nov 2022 none GPL-3.0 — Details →
0.8.2 27 Sep 2022 none GPL-3.0 — Details →
0.8.1 29 Mar 2022 none GPL-3.0 — Details →
0.6.3 28 Mar 2022 none GPL-3.0 — Details →
0.8.0 24 Mar 2022 none GPL-3.0 — Details →
0.6.2 17 Feb 2022 none GPL-3.0 — Details →
0.7.0 17 Feb 2022 none GPL-3.0 — Details →
0.6.1 03 Dec 2021 none GPL-3.0 — Details →
0.6.0 11 Nov 2021 none GPL-3.0 — Details →
0.5.2 24 Jun 2021 none GPL-3.0 — Details →
0.5.1 15 Jun 2021 none GPL-3.0 — Details →
0.5.0 15 Jun 2021 none GPL-3.0 — Details →
0.4.0 07 Jun 2021 none GPL-3.0 — Details →
0.3.0 05 Nov 2020 none GPL-3.0 — Details →
0.2.4 04 Oct 2019 none GPL-3.0 — Details →
0.2.3 11 Jun 2019 none GPL-3.0 — Details →
0.2.2 08 Jan 2019 none GPL-3.0 — Details →
0.1.11 20 Sep 2018 none GPL-3.0 — Details →
0.2.1 20 Sep 2018 none GPL-3.0 — Details →
0.2.0 05 Apr 2018 C1 GPL-3.0 Yes Details →
0.1.10 27 Jan 2018 none GPL-3.0 — Details →
0.1.9 23 Jan 2018 none GPL-3.0 — Details →
0.1.8 04 Oct 2017 none GPL-3.0 — Details →
0.1.7 15 Aug 2017 none GPL-3.0 — Details →
0.1.6 09 May 2017 none GPL-3.0 — Details →
0.1.5 08 Sep 2016 none GPL-3.0 — Details →
0.1.4 18 Aug 2016 none GPL-3.0 — Details →
0.1.3 20 Jun 2016 none GPL-3.0 — Details →
0.1.2 15 Jun 2016 none GPL-3.0 — Details →
0.1.1 10 Jun 2016 none GPL-3.0 — Details →
0.1.0 01 Jun 2016 none GPL-3.0 — Details →
0.0.7 16 Feb 2016 none GPL-3.0 — Details →
0.0.6 04 Feb 2016 none GPL-3.0 — Details →
0.0.5 21 Jan 2016 none GPL-3.0 — Details →
0.0.4 22 Sep 2015 none GPL-3.0 — Details →
0.0.3 14 Aug 2015 none GPL-3.0 — Details →
0.0.2 14 Aug 2015 none GPL-3.0 — Details →
0.0.1 13 Aug 2015 none GPL-3.0 — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1

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

03 Vulnerabilities

Recorded vulnerabilities for smart_proxy_dynflow

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-14643: Improper Authentication in smart_proxy_dynflow 9.8 critical 0.2.1 08 Oct 2018

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 smart_proxy_dynflow

Is smart_proxy_dynflow safe to use?

Vulert records 1 vulnerabilities for smart_proxy_dynflow in RubyGems: 1 critical, 0 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is smart_proxy_dynflow's Vulert package health score?

Vulert scores smart_proxy_dynflow 87/100, which reads as healthy. 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).

Is the latest version of smart_proxy_dynflow affected?

No. 1.0.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of smart_proxy_dynflow should I use?

1.0.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does smart_proxy_dynflow have?

1 vulnerability is recorded for smart_proxy_dynflow in the RubyGems ecosystem: 1 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new smart_proxy_dynflow vulnerabilities disclosed?

0 vulnerabilities were recorded for smart_proxy_dynflow in the last 12 months, and the oldest entry in this database dates to 08 Oct 2018. 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 smart_proxy_dynflow 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 smart_proxy_dynflow for upcoming vulnerabilities?

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