Authorization bypass in Spree

Answer in brief

CVE-2020-26223 records a High severity (CVSS 7.7) vulnerability in Authorization bypass in Spree. The current sources do not mark it as known exploited. The current feed maps spree_api (rubygems), spree_api (rubygems), spree_api (rubygems). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Nov 13, 2020Updated Sep 10, 2026Source checked Sep 10, 2026First seen by HOL Aug 7, 2026Material review Sep 10, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 7.7
Exploitation: Not marked as known exploited
Affected software: 3 mapped packages or products
Fix availability: Available

Why this deserves its current priority

CVSS is 7.7. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps spree_api (rubygems), spree_api (rubygems), spree_api (rubygems). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
spree_apirubygems	>=3.7.0 <3.7.13	3.7.13
spree_apirubygems	>=4.0.0 <4.0.5	4.0.5
spree_apirubygems	>=4.1.0 <4.1.12	4.1.12

Recommended response

Check inventory. Check lockfiles and deployed manifests for spree_api, spree_api, spree_api.
Review the reported fix. Update spree_api to 3.7.13; spree_api to 4.0.5; spree_api to 4.1.12 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Nov 13, 2020
Evidence: source:osv:source_dates:source-dates:record
Source modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:record
First seen by HOL
Aug 7, 2026

Sources and claim methodology

Upstream source description

### Impact The perpetrator could query the [API v2 Order Status](https://guides.spreecommerce.org/api/v2/storefront#tag/Order-Status) endpoint with an empty string passed as an Order token ### Patches Please upgrade to 3.7.11, 4.0.4, or 4.1.11 depending on your used Spree version. Users of Spree < 3.7 are not affected. ### References Pull request with a fix and in-depth explanation - https://github.com/spree/spree/pull/10573 ### For more information If you have any questions or comments about this advisory: * Email us at [[email protected]](mailto:[email protected])

Quoted source text, attributed separately from HOL analysis.