VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

spree_api: vulnerability history, versions and safety

spree_api is a package in the RubyGems ecosystem. Vulert records 4 vulnerabilities for it across 27 releases, from Nov 2020 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H3 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 22 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all spree_api vulnerabilities

Vulert verdict on spree_api 5.6.1 i

Updated on 23 Oct 2026

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

Package health score 83/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 5.6.1 — unaffected i
  • Vulnerabilities on record 4 over 5 years · 3 in the last year i
  • Latest disclosure 22 Sep 2026 i
  • Highest CVSS 7.7 i
  • With no published fix 0 i
  • Stars 15,761 i
  • OpenSSF scorecard 5/10 i
  • Last release 2 months ago i
  • Licence BSD-3-Clause i

Version list, release dates, licence and dependants published by RubyGems, refreshed 22 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 spree_api, 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
6.0.0.rc5 22 Oct 2026 none BSD-3-Clause — Details →
6.0.0.rc4 19 Oct 2026 none BSD-3-Clause — Details →
6.0.0.rc3 13 Oct 2026 none BSD-3-Clause — Details →
6.0.0.rc2 13 Oct 2026 none BSD-3-Clause — Details →
6.0.0.rc1 08 Oct 2026 none BSD-3-Clause — Details →
6.0.0.beta4 24 Sep 2026 none BSD-3-Clause — Details →
6.0.0.beta3 24 Sep 2026 none BSD-3-Clause — Details →
6.0.0.beta2 17 Sep 2026 none BSD-3-Clause — Details →
6.0.0.beta1 15 Sep 2026 none BSD-3-Clause — Details →
5.6.1 28 Jul 2026 none BSD-3-Clause — Details →
5.6.0 23 Jul 2026 none BSD-3-Clause — Details →
5.6.0.rc6 23 Jul 2026 none BSD-3-Clause — Details →
5.6.0.rc5 22 Jul 2026 none BSD-3-Clause — Details →
5.6.0.rc4 20 Jul 2026 none BSD-3-Clause — Details →
5.5.4 20 Jul 2026 none BSD-3-Clause — Details →
5.4.4 20 Jul 2026 none BSD-3-Clause — Details →
5.6.0.rc3 19 Jul 2026 none BSD-3-Clause — Details →
5.6.0.rc2 17 Jul 2026 none BSD-3-Clause — Details →
5.6.0.rc1 15 Jul 2026 none BSD-3-Clause — Details →
5.5.3 10 Jul 2026 none BSD-3-Clause — Details →
5.5.2 06 Jul 2026 none BSD-3-Clause — Details →
5.5.1 29 Jun 2026 none BSD-3-Clause — Details →
5.5.0 18 Jun 2026 none BSD-3-Clause — Details →
5.5.0.rc3 18 Jun 2026 none BSD-3-Clause — Details →
5.5.0.rc2 15 Jun 2026 none BSD-3-Clause — Details →
5.5.0.rc1 10 Jun 2026 none BSD-3-Clause — Details →
5.3.6 19 May 2026 none AGPL-3.0-or-later — Details →
5.2.8 19 May 2026 none AGPL-3.0-or-later — Details →
5.4.3 19 May 2026 H1 BSD-3-Clause Yes Details →
5.4.2 27 Apr 2026 H1 BSD-3-Clause Yes Details →
5.4.1 14 Apr 2026 H1 BSD-3-Clause Yes Details →
5.4.0 08 Apr 2026 H1 BSD-3-Clause Yes Details →
5.4.0.rc8 08 Apr 2026 none BSD-3-Clause — Details →
5.4.0.rc7 08 Apr 2026 none BSD-3-Clause — Details →
5.4.0.rc6 04 Apr 2026 none BSD-3-Clause — Details →
5.4.0.rc5 30 Mar 2026 none BSD-3-Clause — Details →
5.4.0.rc4.1 30 Mar 2026 none BSD-3-Clause — Details →
5.4.0.rc4 26 Mar 2026 none BSD-3-Clause — Details →
5.4.0.rc3 25 Mar 2026 none BSD-3-Clause — Details →
5.4.0.rc2 23 Mar 2026 none BSD-3-Clause — Details →
5.4.0.rc1 20 Mar 2026 none BSD-3-Clause — Details →
5.4.0.beta10 19 Mar 2026 none BSD-3-Clause — Details →
5.4.0.beta9 17 Mar 2026 none BSD-3-Clause — Details →
5.4.0.beta8 16 Mar 2026 none BSD-3-Clause — Details →
5.4.0.beta7 15 Mar 2026 none BSD-3-Clause — Details →
5.3.5 12 Mar 2026 none AGPL-3.0-or-later — Details →
5.4.0.beta6 11 Mar 2026 none BSD-3-Clause — Details →
5.4.0.beta5 10 Mar 2026 none BSD-3-Clause — Details →
5.4.0.beta4 04 Mar 2026 none BSD-3-Clause — Details →
5.4.0.beta3 02 Mar 2026 none BSD-3-Clause — Details →
5.4.0.beta2 28 Feb 2026 none BSD-3-Clause — Details →
5.4.0.beta 25 Feb 2026 none BSD-3-Clause — Details →
5.3.4 23 Feb 2026 none AGPL-3.0-or-later — Details →
5.3.3 16 Feb 2026 none AGPL-3.0-or-later — Details →
4.10.3 05 Feb 2026 none AGPL-3.0-or-later — Details →
5.0.8 05 Feb 2026 none AGPL-3.0-or-later — Details →
5.1.10 05 Feb 2026 none AGPL-3.0-or-later — Details →
5.2.7 05 Feb 2026 none AGPL-3.0-or-later — Details →
5.3.2 05 Feb 2026 none AGPL-3.0-or-later — Details →
5.3.1 02 Feb 2026 none AGPL-3.0-or-later — Details →
5.3.0 26 Jan 2026 none AGPL-3.0-or-later — Details →
5.3.0.rc2 22 Jan 2026 none AGPL-3.0-or-later — Details →
5.3.0.rc1 22 Jan 2026 none AGPL-3.0-or-later — Details →
5.2.6 15 Jan 2026 none AGPL-3.0-or-later — Details →
4.10.2 08 Jan 2026 H1 AGPL-3.0-or-later Yes Details →
5.0.7 08 Jan 2026 none AGPL-3.0-or-later — Details →
5.1.9 08 Jan 2026 none AGPL-3.0-or-later — Details →
5.2.5 08 Jan 2026 none AGPL-3.0-or-later — Details →
5.2.4 18 Dec 2025 none AGPL-3.0-or-later — Details →
5.2.3 16 Dec 2025 none AGPL-3.0-or-later — Details →
5.2.2 09 Dec 2025 none AGPL-3.0-or-later — Details →
5.2.1 02 Dec 2025 none AGPL-3.0-or-later — Details →
5.2.0 27 Nov 2025 none AGPL-3.0-or-later — Details →
5.2.0.rc3 18 Nov 2025 none AGPL-3.0-or-later — Details →
5.2.0.rc2 09 Nov 2025 none AGPL-3.0-or-later — Details →
5.2.0.rc1 04 Nov 2025 none AGPL-3.0-or-later — Details →
5.1.8 30 Oct 2025 none AGPL-3.0-or-later — Details →
5.1.7 29 Sep 2025 none AGPL-3.0-or-later — Details →
5.1.6 18 Sep 2025 none AGPL-3.0-or-later — Details →
5.1.5 06 Aug 2025 none AGPL-3.0-or-later — Details →
5.0.6 06 Aug 2025 none AGPL-3.0-or-later — Details →
5.1.4 24 Jul 2025 none AGPL-3.0-or-later — Details →
5.1.3 20 Jul 2025 none AGPL-3.0-or-later — Details →
5.1.2 14 Jul 2025 none AGPL-3.0-or-later — Details →
5.1.1 08 Jul 2025 none AGPL-3.0-or-later — Details →
5.1.0 03 Jul 2025 none AGPL-3.0-or-later — Details →
5.1.0.rc1 02 Jul 2025 none AGPL-3.0-or-later — Details →
5.0.5 30 Jun 2025 none AGPL-3.0-or-later — Details →
5.1.0.beta4 04 Jun 2025 none AGPL-3.0-or-later — Details →
5.1.0.beta3 29 May 2025 none AGPL-3.0-or-later — Details →
5.1.0.beta2 22 May 2025 none AGPL-3.0-or-later — Details →
5.0.4 22 May 2025 none AGPL-3.0-or-later — Details →
5.1.0.beta 20 May 2025 none AGPL-3.0-or-later — Details →
5.0.3 06 May 2025 none AGPL-3.0-or-later — Details →
5.0.2 22 Apr 2025 none AGPL-3.0-or-later — Details →
5.0.1 09 Apr 2025 none AGPL-3.0-or-later — Details →
5.0.0 03 Apr 2025 none AGPL-3.0-or-later — Details →
5.0.0.rc1 01 Apr 2025 none AGPL-3.0-or-later — Details →
4.10.1 06 Sep 2024 H1 M1 AGPL-3.0-or-later Yes Details →
4.10.0 06 Sep 2024 H1 M1 AGPL-3.0-or-later Yes Details →
4.9.0 14 Aug 2024 H1 M1 — Yes Details →
4.8.3 13 Jun 2024 H1 M1 — Yes Details →
4.8.2 29 May 2024 H1 M1 — Yes Details →
4.8.1 27 May 2024 H1 M1 — Yes Details →
4.8.0 23 May 2024 H1 M1 — Yes Details →
4.7.3 24 Apr 2024 H1 M1 — Yes Details →
4.6.6 24 Apr 2024 H1 M1 — Yes Details →
4.5.5 24 Apr 2024 H1 M1 — Yes Details →
4.0.9 21 Apr 2024 H1 M1 — Yes Details →
4.1.15 21 Apr 2024 H1 M1 — Yes Details →
4.2.7 21 Apr 2024 H1 M1 — Yes Details →
4.3.3 21 Apr 2024 H1 M1 — Yes Details →
4.4.1 21 Apr 2024 H1 M1 — Yes Details →
4.5.4 21 Apr 2024 H1 M1 — Yes Details →
4.6.5 21 Apr 2024 H1 M1 — Yes Details →
4.7.2 21 Apr 2024 H1 M1 — Yes Details →
4.7.1 09 Jan 2024 H1 M1 — Yes Details →
4.6.4 09 Jan 2024 H1 M1 — Yes Details →
4.7.0 09 Nov 2023 H1 M1 — Yes Details →
4.6.3 09 Nov 2023 H1 M1 — Yes Details →

The newest 120 of 419 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1
  • 2026 3

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

03 Vulnerabilities

Recorded vulnerabilities for spree_api

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-26223: Authorization bypass in Spree 7.7 high 3.7.13 13 Nov 2020
Critical IDOR Vulnerability in Spree Commerce Allows Unauthenticated Access to Guest Addresses 7.7 high 4.10.3 05 Feb 2026
CVE-2026-94462: Spree API Vulnerability - Broken Access Control in Cart Association 7.1 high 5.4.4 22 Sep 2026
CVE-2026-22588: Spree API Authenticated Insecure Direct Object Reference (IDOR) Vulnerability 6.5 medium 4.10.2 08 Jan 2026

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 spree_api

Is spree_api safe to use?

Vulert records 4 vulnerabilities for spree_api in RubyGems: 0 critical, 3 high, 1 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 spree_api's Vulert package health score?

Vulert scores spree_api 83/100, which reads as in good shape. 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 spree_api affected?

No. 5.6.1, 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 spree_api should I use?

5.6.1 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 spree_api have?

4 vulnerabilities are recorded for spree_api in the RubyGems ecosystem: 0 critical, 3 high, 1 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 spree_api vulnerabilities disclosed?

3 vulnerabilities were recorded for spree_api in the last 12 months, and the oldest entry in this database dates to 13 Nov 2020. 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 spree_api 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 spree_api for upcoming vulnerabilities?

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