Spree is an open source e-commerce solution built with Ruby on Rails. From 5.4.0 until 5.4.4 and 5.5.4, PATCH /api/v3/store/carts/:id/associate in Spree::Api::V3::Store::CartsController#associate uses find_cart_for_association to locate a cart by prefixed_id but does not require a cart token or otherwise verify possession of the selected guest cart. An authenticated customer can derive reversible prefixed cart IDs, associate an eligible guest cart with the attacker's account, and receive billing and shipping address data from the cart. Exploitation requires a guest cart with address data on a store that does not require login for checkout, and reassignment can also disrupt the guest's in-progress cart. This issue is fixed in versions 5.4.4 and 5.5.4.
CVE-2026-94462
“—” beside the score: it is equal to the CVSS score beside it.
Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-09-22. A secondary CVSS source baseline 7.1; sources differ by 0.0.
Also known asEUVD-2026-84794 (ENISA EUVD) · GHSA-4825-p4xm-pcf2 (GitHub Security Advisories)Source: ENISA EUVD
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 7.1
- EG Score
- 7.1HIGHmedium confidence
- EG Risk
- 48EG Risk 48/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity71% × 45%Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.4%
- EPSS %ILE
- 32nd
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
September 22, 2026
Last Modified
September 23, 2026
Advisory Details (6)
Auto-updated Sep 22, 2026v5.5.4
Patch available: spree/spree v5.5.4
https://github.com/spree/spree/releases/tag/v5.5.4v5.4.4
Patch available: spree/spree v5.4.4
https://github.com/spree/spree/releases/tag/v5.4.4commit af0d1a2d582a (spree/spree)
Patch available: spree/spree v5.5.4 (contains commit af0d1a2d582a)
https://github.com/spree/spree/commit/af0d1a2d582a60d179de65b7d3ea024cb26426a8commit 8834230a1f47 (spree/spree)
Patch available: spree/spree v5.4.4 (contains commit 8834230a1f47)
https://github.com/spree/spree/commit/8834230a1f47bb5988f23f45dbd162776cf592bdHarden Store API Cart Associate endpoint
Patch available: spree/spree v5.6.0 (PR #14314 merged 2026-07-16)
https://github.com/spree/spree/pull/14314Broken Access Control in `PATCH /api/v3/store/carts/:id/associate` (IDOR) · Advisory · spree/spree · GitHub
https://github.com/spree/spree/security/advisories/GHSA-4825-p4xm-pcf2Vendor Advisories for CVE-2026-94462(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(2)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| rubygems | spree_api @ 5.4.4 (fixes >= 5.4.0, < 5.4.4) | — | ghsa |
| rubygems | spree_api @ 5.5.4 (fixes >= 5.5.0, < 5.5.4) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
RubyGems(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| spree_api | 5.5.0, 5.5.1, 5.5.2, 5.5.3 |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 50× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 75 is merged into the row it repeats.
- 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-11-01 07:37 UTCGHSA enrichmentGHSA-4825-p4xm-pcf2 · GitHub severity HIGH · GitHub CVSS 7.1
- 2026-11-01 07:37 UTCEG score recompute
- 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-27 18:53 UTCEG score recompute
- 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-25 13:49 UTCEG score recompute
- 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-10-20 06:50 UTCEG score recompute
- 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-10-18 02:58 UTCEG score recompute
- 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
Show 49 moreShow fewer
- 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-10-13 04:18 UTCEG score recompute
- 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-10-12 14:41 UTCEG score recompute
- 2026-10-11 19:12 UTCEG score recompute
- 2026-10-11 16:27 UTCEG score recompute
- 2026-10-11 14:33 UTCEG score recompute
- 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-10-11 13:40 UTCEG score recompute
- 2026-10-11 01:40 UTCEG score recompute
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-10-09 22:34 UTCEG score recompute
- 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-10-08 20:43 UTCEG score recompute
- 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-10-08 07:49 UTCEG score recompute
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-10-06 17:08 UTCEG score recompute
- 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-10-06 04:16 UTCEG score recompute
- 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-10-05 02:27 UTCEG score recompute
- 2026-10-04 23:23 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-10-04 00:41 UTCEG score recompute
- 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-10-02 22:19 UTCEG score recompute
- 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-10-01 20:34 UTCEG score recompute
- 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-09-30 18:48 UTCEG score recompute
- 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-09-29 16:48 UTCEG score recompute
- 2026-09-29 03:35 UTCEG score recompute
- 2026-09-28 14:42 UTCEG score recompute
- 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-09-28 01:49 UTCEG score recompute
- 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-09-27 00:04 UTCEG score recompute
- 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-09-26 11:11 UTCEG score recompute
- 2026-09-24 20:12 UTCEG score recompute
- 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-09-23 18:26 UTCEG score recompute
- 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-09-22 20:32 UTCEG score recompute
- 2026-09-22 19:33 UTCEG score recompute
- 2026-09-22 18:58 UTCEG score recomputeFirst assessed: 7.1 HIGH
- 2026-09-22 18:58 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
3 shownRubyGems:spree_api
Frequently asked(5)
What is CVE-2026-94462?
When was the CVE record for CVE-2026-94462 published?
Is CVE-2026-94462 actively exploited?
What is the CVSS score of CVE-2026-94462?
How do I remediate CVE-2026-94462?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-94462
Is Your Infrastructure Affected by CVE-2026-94462?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.