CVE-2026-22588: Spree api Spree API Has Authenticated Insecure Vulnerability

MODERATE
Advisory Identifier: GHSA-g268-72p7-9j6j
CVSS 6.5
CWE-639
Published
Advisory Summary

CVE-2026-22588 is a MODERATE (CVSS 6.5) spree api has authenticated insecure vulnerability (CWE-639: Authorization Bypass Through User-Controlled Key) affecting Spree api libraries in the RubyGems ecosystem. The issue involves spree api has authenticated insecure direct object reference (idor) via order modification. Remediation is available by upgrading affected packages to version 4.10.2, 5.0.7, 5.1.9, 5.2.5.

CVE-2026-22588 at a Glance

CVE Identifier CVE-2026-22588
GHSA Identifier GHSA-g268-72p7-9j6j
Severity MODERATE
CVSS v3.1 Base Score 6.5
CWE Classification CWE-639: Authorization Bypass Through User-Controlled Key
Affected Product Spree api
Package Ecosystem RubyGems
Published Date
Last Updated

Security Impact

CVSS: 6.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-22588

To remediate this vulnerability, upgrade all affected Spree api dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

spree_api fixed: 4.10.2
Upgrade spree_api to 4.10.2
spree_api fixed: 5.0.7
Upgrade spree_api to 5.0.7
spree_api fixed: 5.1.9
Upgrade spree_api to 5.1.9
spree_api fixed: 5.2.5
Upgrade spree_api to 5.2.5
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for spree_api

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-22588, inspect your project dependencies for Spree api:

inspect dependencies for spree_api

Analyze the terminal output to locate any version of Spree api in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.10.2), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-639: Authorization Bypass Through User-Controlled Key, where the system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. In Spree api, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary An Authenticated Insecure Direct Object Reference (IDOR) vulnerability was identified that allows an authenticated user to retrieve other users’ address information by modifying an existing order. By editing an order they legitimately own and manipulating address identifiers in the request, the backend server accepts and processes references to addresses belonging to other users, subsequently associating those addresses with the attacker’s order and returning them in the response. ### Details Affected Component(s) - Authenticated user order management - Address association logic - Order update endpoint(s) Affected Endpoint(s): - `/api/v2/storefront/checkout` The application fails to enforce proper object-level authorization when updating an existing order. While the user is authenticated and authorized to modify their own order, the backend does not verify that the supplied address identifiers belong to the same authenticated user. ### PoC Preconditions - Valid authenticated user account Step 1: Log-in using a valid user, in this case customer2@example.com Step 2: Visualize current user’s addresses **Request** GET `/account/addresses` The following screenshot shows customer2@example.com address. <img width="336" height="375" alt="User Address" src="https://github.com/user-attachments/assets/ceb1f214-7ac0-40b0-af22-6fe9d21254bb" /> Step 3: Initialize the Shopping Cart **Request** POST `/api/v2/storefront/cart HTTP/1.1` From the response, extract the token marked in bold. Step 4: Legitimate Order Edit Request Using the obtained order token **A1cram_6cFWpoj4V1yPkuQ1767113871701** perform an edit order request in order to add a custom billing address **Request** PATCH `/api/v2/storefront/checkout` ```json { "include": "billing_address", "order": { "email": "idor_test@example.com", "bill_address_attributes": { "firstname":"CTF","lastname":"Tester","address1":"123 Main St", "city":"Andorra la Vella","zipcode":"AD100","country_iso":"AD" }, "ship_address_attributes": { "firstname":"CTF","lastname":"Tester","address1":"123 Main St", "city":"Andorra la Vella","zipcode":"AD100","country_iso":"AD" } } } ``` Step 5: Modify the order request to include the other user's address and trigger the IDOR. In this request, the attacker modifies the request by substituting the address identifier with one belonging to another user, thereby rendering the original address identifier accessible to the attacker. **Request** PATCH `/api/v2/storefront/checkout` ```json {"include":"billing_address","order":**{"bill_address_attributes":{"id":1}}**} ``` As can be seen other user's address is displayed. ### Impact As a result, an attacker can: - Replace the address identifier with one belonging to another user - Cause the backend to associate and return another user’s address within the attacker’s order

CVE-2026-22588 Affected Spree api Versions

4 component(s)
Fixed Versions:
4.10.25.0.75.1.95.2.5
Product / Package Ecosystem Affected Versions Fixed Version
spree_api
RubyGems
≥ 3.7.0
< 4.10.2
4.10.2
spree_api
RubyGems
≥ 5.0.0
< 5.0.7
5.0.7
spree_api
RubyGems
≥ 5.1.0
< 5.1.9
5.1.9
spree_api
RubyGems
≥ 5.2.0
< 5.2.5
5.2.5

References

Frequently Asked Questions

What is CVE-2026-22588?
CVE-2026-22588 is a security vulnerability in Spree api involving Spree API has Authenticated Insecure Direct Object Reference (IDOR) via Order Modification under CWE-639: Authorization Bypass Through User-Controlled Key.
Which Spree api versions are affected?
Affected versions include releases prior to 4.10.2, 5.0.7, 5.1.9, 5.2.5 across affected packages: spree_api.
What version fixes CVE-2026-22588?
Upgrading to 4.10.2, 5.0.7, 5.1.9, 5.2.5 (or the latest patched release for your respective branch) resolves the vulnerability.
Is spree_api affected?
Yes, spree_api is affected in releases prior to 4.10.2, 5.0.7, 5.1.9, 5.2.5. Upgrade your dependency to 4.10.2, 5.0.7, 5.1.9, 5.2.5 or later.
What is the CVSS score of CVE-2026-22588?
CVE-2026-22588 has a CVSS v3.1 base score of 6.5 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2026-22588?
CVE-2026-22588 is classified under CWE-639: Authorization Bypass Through User-Controlled Key (The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.).
How can I check RubyGems dependencies for CVE-2026-22588?
Run the dependency tree command: 'inspect dependencies for spree_api'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-g268-72p7-9j6j",
  "modified" : "2026-01-11T14:57:07Z",
  "published" : "2026-01-08T21:27:03Z",
  "aliases" : [ "CVE-2026-22588" ],
  "summary" : "Spree API has Authenticated Insecure Direct Object Reference (IDOR) via Order Modification",
  "details" : "### Summary\nAn Authenticated Insecure Direct Object Reference (IDOR) vulnerability was identified that allows an authenticated user to retrieve other users’ address information by modifying an existing order.\nBy editing an order they legitimately own and manipulating address identifiers in the request, the backend server accepts and processes references to addresses belonging to other users, subsequently associating those addresses with the attacker’s order and returning them in the response.\n\n### Details\nAffected Component(s)\n- Authenticated user order management\n- Address association logic\n- Order update endpoint(s)\nAffected Endpoint(s):\n- `/api/v2/storefront/checkout`\n\nThe application fails to enforce proper object-level authorization when updating an existing order. While the user is authenticated and authorized to modify their own order, the backend does not verify that the supplied address identifiers belong to the same authenticated user.\n\n### PoC\nPreconditions\n- Valid authenticated user account\n\nStep 1: Log-in using a valid user, in this case customer2@example.com\nStep 2: Visualize current user’s addresses \n\n**Request**\nGET `/account/addresses`\n\nThe following screenshot shows customer2@example.com address. \n\n<img width=\"336\" height=\"375\" alt=\"User Address\" src=\"https://github.com/user-attachments/assets/ceb1f214-7ac0-40b0-af22-6fe9d21254bb\" />\n\nStep 3: Initialize the Shopping Cart\n\n**Request**\nPOST `/api/v2/storefront/cart HTTP/1.1`\n\nFrom the response, extract the token marked in bold.\n\nStep 4: Legitimate Order Edit Request\n\nUsing the obtained order token **A1cram_6cFWpoj4V1yPkuQ1767113871701** perform an edit order  request in order to add a custom billing address\n\n**Request**\nPATCH `/api/v2/storefront/checkout`\n\n```json\n{\n    \"include\": \"billing_address\",\n    \"order\": {\n      \"email\": \"idor_test@example.com\",\n      \"bill_address_attributes\": {\n        \"firstname\":\"CTF\",\"lastname\":\"Tester\",\"address1\":\"123 Main St\",\n        \"city\":\"Andorra la Vella\",\"zipcode\":\"AD100\",\"country_iso\":\"AD\"\n      },\n      \"ship_address_attributes\": {\n        \"firstname\":\"CTF\",\"lastname\":\"Tester\",\"address1\":\"123 Main St\",\n        \"city\":\"Andorra la Vella\",\"zipcode\":\"AD100\",\"country_iso\":\"AD\"\n      }\n    }\n  }\n```\n\nStep 5: Modify the order request to include the other user's address and trigger the IDOR.\n\nIn this request, the attacker modifies the request by substituting the address identifier with one belonging to another user, thereby rendering the original address identifier accessible to the attacker.\n\n**Request**\nPATCH `/api/v2/storefront/checkout`\n\n```json\n{\"include\":\"billing_address\",\"order\":**{\"bill_address_attributes\":{\"id\":1}}**}\n```\n\nAs can be seen other user's address is displayed.\n\n### Impact\nAs a result, an attacker can:\n\n- Replace the address identifier with one belonging to another user\n- Cause the backend to associate and return another user’s address within the attacker’s order",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "RubyGems",
      "name" : "spree_api"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.7.0"
      }, {
        "fixed" : "4.10.2"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "RubyGems",
      "name" : "spree_api"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "5.0.0"
      }, {
        "fixed" : "5.0.7"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "RubyGems",
      "name" : "spree_api"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "5.1.0"
      }, {
        "fixed" : "5.1.9"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "RubyGems",
      "name" : "spree_api"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "5.2.0"
      }, {
        "fixed" : "5.2.5"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/spree/spree/security/advisories/GHSA-g268-72p7-9j6j"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-22588"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/spree/spree/commit/02acabdce2c5f14fd687335b068d901a957a7e72"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/spree/spree/commit/17e78a91b736b49dbea8d1bb1223c284383ee5f3"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/spree/spree/commit/b409c0fd327e7ce37f63238894670d07079eefe8"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/spree/spree/commit/d3f961c442e0015661535cbd6eb22475f76d2dc7"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/rubysec/ruby-advisory-db/blob/master/gems/spree_api/CVE-2026-22588.yml"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/spree/spree"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-639" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-01-08T21:27:03Z",
    "nvd_published_at" : "2026-01-08T21:15:44Z"
  }
}