# CVE-2026-94462: Spree: Broken Access Control in `PATCH /api/v3/store/carts/:id/associate` (IDOR)

> Authenticated users can hijack guest carts and steal address data due to missing authorization checks in the cart association API.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-4825-p4xm-pcf2

## What is CVE-2026-94462?

CVE-2026-94462 is a high-severity missing authorization vulnerability in spree, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-94462?

4 open source packages ship an affected version, including spree_api.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `spree_api` | RubyGems | From 5.4.0 | 5.4.4 |
| `spree_api` | RubyGems | From 5.4.0 | 5.4.4 |
| `spree_api` | RubyGems | From 5.5.0 | 5.5.4 |
| `spree_api` | RubyGems | From 5.5.0 | 5.5.4 |

## How do I fix CVE-2026-94462?

Upgrade spree_api to a fixed version for your release line: 5.4.4 or 5.5.4.

## Is CVE-2026-94462 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-94462 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-94462 and fix it if it is affected.

What it is: CVE-2026-94462 is a high-severity missing authorization vulnerability in spree, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-94462 exists.

Affected packages and fixed versions:
- spree_api (RubyGems): affected from 5.4.0; fixed in 5.4.4
- spree_api (RubyGems): affected from 5.4.0; fixed in 5.4.4
- spree_api (RubyGems): affected from 5.5.0; fixed in 5.5.4
- spree_api (RubyGems): affected from 5.5.0; fixed in 5.5.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-94462/ (Markdown: https://insights.sbomify.com/CVE-2026-94462/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-94462
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-94462
- OSV: https://osv.dev/vulnerability/CVE-2026-94462

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-94462/
Summaries are generated and may contain mistakes; the official description above is the record.