VulertSecurity VulertSecurity

Vulnerability Database · NuGet · Package report

recurly-api-client: vulnerability history, versions and safety

recurly-api-client is a package in the NuGet ecosystem. Vulert records 1 vulnerability for it across 0 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 recurly-api-client vulnerabilities

Vulert verdict on recurly-api-client 2.0.0 i

Updated on 23 Oct 2026

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

Package health score 96/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Not enough data
  • Community Not enough data

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

  • Current release 2.0.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 16 Oct 2018 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Last release 10 months ago i

Version list, release dates, licence and dependants published by NuGet, 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 recurly-api-client, 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.18.7 17 Dec 2025 none — — Details →
1.18.6 10 Dec 2025 none — — Details →
1.18.5 07 Apr 2025 none — — Details →
1.18.4 13 Nov 2024 none — — Details →
1.18.3 28 Aug 2024 none — — Details →
1.18.2 21 Aug 2024 none — — Details →
1.18.1 03 Jul 2024 none — — Details →
1.18.0 08 May 2024 none — — Details →
1.17.38 04 Apr 2024 none — — Details →
1.17.37 19 Mar 2024 none — — Details →
1.17.36 13 Mar 2024 none — — Details →
1.17.34 06 Dec 2023 none — — Details →
1.17.33 01 Aug 2023 none — — Details →
1.17.31 13 Jun 2023 none — — Details →
1.17.30 30 May 2023 none — — Details →
1.17.28 26 Apr 2023 none — — Details →
1.17.27 13 Apr 2023 none — — Details →
1.17.26 05 Apr 2023 none — — Details →
1.17.25 22 Feb 2023 none — — Details →
1.17.24 06 Feb 2023 none — — Details →
1.17.23 11 Jan 2023 none — — Details →
1.17.22 30 Nov 2022 none — — Details →
1.17.21 15 Nov 2022 none — — Details →
1.17.20 10 Nov 2022 none — — Details →
1.17.19 27 Oct 2022 none — — Details →
1.17.18 20 Oct 2022 none — — Details →
1.17.17 31 Aug 2022 none — — Details →
1.17.16 24 Aug 2022 none — — Details →
1.17.15 17 Jun 2022 none non-standard — Details →
1.17.14 09 Mar 2022 none non-standard — Details →
1.17.13 27 Oct 2021 none non-standard — Details →
1.17.12 16 Jun 2021 none non-standard — Details →
1.17.11 22 Apr 2021 none non-standard — Details →
1.17.10 22 Feb 2021 none non-standard — Details →
1.17.9 05 Nov 2020 none non-standard — Details →
1.17.8 17 Sep 2020 none non-standard — Details →
1.17.7 20 Aug 2020 none non-standard — Details →
1.17.6 22 Jul 2020 none non-standard — Details →
1.17.5 30 Jun 2020 none non-standard — Details →
1.17.4 15 Apr 2020 none non-standard — Details →
1.17.3 27 Mar 2020 none non-standard — Details →
1.17.2 20 Feb 2020 none non-standard — Details →
1.17.1 18 Feb 2020 none non-standard — Details →
1.17.0 21 Nov 2019 none non-standard — Details →
1.16.3 22 Oct 2019 none non-standard — Details →
1.16.2 13 Sep 2019 none non-standard — Details →
1.16.1 21 Aug 2019 none non-standard — Details →
1.16.0 16 Jul 2019 none non-standard — Details →
1.15.8 27 Jun 2019 none non-standard — Details →
1.15.7 18 Jun 2019 none non-standard — Details →
1.15.6 21 May 2019 none non-standard — Details →
1.15.5 30 Apr 2019 none non-standard — Details →
1.15.4 19 Mar 2019 none non-standard — Details →
1.15.3 12 Mar 2019 none non-standard — Details →
1.15.2 19 Feb 2019 none non-standard — Details →
1.15.1 07 Feb 2019 none non-standard — Details →
1.15.0 05 Feb 2019 none non-standard — Details →
1.14.1 11 Dec 2018 none non-standard — Details →
1.14.0 30 Oct 2018 none non-standard — Details →
1.13.1 25 Sep 2018 none non-standard — Details →
1.13.0 12 Sep 2018 none non-standard — Details →
1.13.0-alpha 12 Sep 2018 none non-standard — Details →
1.12.5 30 Jul 2018 none non-standard — Details →
1.12.4 06 Jul 2018 none non-standard — Details →
1.12.3 27 Jun 2018 none non-standard — Details →
1.12.2 26 Jun 2018 none non-standard — Details →
1.12.1 22 Jun 2018 none non-standard — Details →
1.12.0 29 May 2018 none non-standard — Details →
1.11.4 16 May 2018 none non-standard — Details →
1.11.3 09 May 2018 none non-standard — Details →
1.10.1 09 May 2018 none non-standard — Details →
1.9.2 09 May 2018 none non-standard — Details →
1.8.2 09 May 2018 none non-standard — Details →
1.7.2 09 May 2018 none non-standard — Details →
1.6.3 09 May 2018 none non-standard — Details →
1.5.4 09 May 2018 none non-standard — Details →
1.4.15 09 May 2018 none non-standard — Details →
1.3.3 09 May 2018 none non-standard — Details →
1.2.9 09 May 2018 none non-standard — Details →
1.1.11 09 May 2018 none non-standard — Details →
1.0.2 09 May 2018 none non-standard — Details →
1.11.2 03 Apr 2018 none non-standard — Details →
1.11.1 02 Apr 2018 none non-standard — Details →
1.11.0 13 Mar 2018 none non-standard — Details →
1.10.0 06 Mar 2018 none non-standard — Details →
1.9.1 23 Jan 2018 none non-standard — Details →
1.9.0 01 Dec 2017 none non-standard — Details →
1.5.3 09 Nov 2017 none non-standard — Details →
1.8.1 09 Nov 2017 none non-standard — Details →
1.7.1 09 Nov 2017 none non-standard — Details →
1.6.2 09 Nov 2017 none non-standard — Details →
1.5.2 09 Nov 2017 none non-standard — Details →
1.4.14 09 Nov 2017 none non-standard — Details →
1.3.2 09 Nov 2017 none non-standard — Details →
1.2.8 09 Nov 2017 none non-standard — Details →
1.1.10 09 Nov 2017 none non-standard — Details →
1.0.1 09 Nov 2017 none non-standard — Details →
1.8.0 27 Oct 2017 none non-standard — Details →
1.7.0 18 Oct 2017 none non-standard — Details →
1.6.1 04 Oct 2017 none non-standard — Details →
1.6.0 06 Sep 2017 none — — Details →
1.5.1 27 Jun 2017 none — — Details →
1.5.0 07 Jun 2017 none — — Details →
1.4.13 04 May 2017 none — — Details →
1.4.12 06 Apr 2017 none — — Details →
1.4.11 17 Feb 2017 none — — Details →
1.4.10 06 Feb 2017 none — — Details →
1.4.9 20 Jan 2017 none — — Details →
1.4.8 20 Jan 2017 none — — Details →
1.4.7 11 Jan 2017 none — — Details →
1.4.6 09 Jan 2017 none — — Details →
1.4.5 06 Dec 2016 none — — Details →
1.4.4 17 Nov 2016 none — — Details →
1.4.3 24 Oct 2016 none — — Details →
1.4.2 03 Oct 2016 none — — Details →
1.4.1 21 Sep 2016 none — — Details →
1.4.0 19 Sep 2016 none — — Details →
1.3.1 19 Nov 2015 none — — Details →
1.3.0 19 Nov 2015 none — — Details →
1.2.7 17 Nov 2015 none — — Details →

The newest 120 of 139 versions Vulert tracks. 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 recurly-api-client

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-0907: Server-Side Request Forgery in recurly-api-client N/A critical 1.0.1 16 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 recurly-api-client

Is recurly-api-client safe to use?

Vulert records 1 vulnerabilities for recurly-api-client in NuGet: 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 recurly-api-client's Vulert package health score?

Vulert scores recurly-api-client 96/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 recurly-api-client affected?

No. 2.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 recurly-api-client should I use?

1.18.7 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 recurly-api-client have?

1 vulnerability is recorded for recurly-api-client in the NuGet 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 recurly-api-client vulnerabilities disclosed?

0 vulnerabilities were recorded for recurly-api-client in the last 12 months, and the oldest entry in this database dates to 16 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 recurly-api-client 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 recurly-api-client for upcoming vulnerabilities?

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