CVE-2026-22589
HIGHCVE-2026-22589 is a high-severity (CVSS 7.5) CWE-639 vulnerability in spree_core. O3 Security confirms whether CVE-2026-22589 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Spree API has Unauthenticated IDOR - Guest Address
Blast Radius
spree_core💎spree_core💎spree_core💎spree_coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.
Description
Spree is an open source e-commerce solution built with Ruby on Rails. Prior to versions 4.10.2, 5.0.7, 5.1.9, and 5.2.5, an Unauthenticated Insecure Direct Object Reference (IDOR) vulnerability was identified that allows an unauthenticated attacker to access guest address information without supplying valid credentials or session cookies. This issue has been patched in versions 4.10.2, 5.0.7, 5.1.9, and 5.2.5.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 💎RubyGems | spree_core | ≥ 4.0.0&&< 4.10.2 | 4.10.2 |
| 💎RubyGems | spree_core | ≥ 5.0.0&&< 5.0.7 | 5.0.7 |
| 💎RubyGems | spree_core | ≥ 5.1.0&&< 5.1.9 | 5.1.9 |
| 💎RubyGems | spree_core | ≥ 5.2.0&&< 5.2.5 | 5.2.5 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for spree_core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update spree_core to 4.10.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-22589 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-22589 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-22589. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-22589 in your dependencies?
O3 detects CVE-2026-22589 across RubyGems dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.