Is CVE-2026-63414 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-63414 being exploited in the wild.

How severe is CVE-2026-63414?

High severity, with a CVSS score of 4, published 30 October 2026.

Which products and versions are affected?

shopify_app (RubyGems) >= 22.1.0, < 23.0.3, ECOSYSTEM:introduced=22.1.0,fixed=23.0.3; Shopify App before 23.0.3.

How is CVE-2026-63414 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-63414?

Check whether you run shopify_app (RubyGems) or Shopify App at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-63414: Shopify shopify_app token-exchange shop context confusion

Q: Is there a fix for CVE-2026-63414?

Yes. shopify_app (RubyGems): upgrade to 23.0.3 or later. Until then: Applications unable to upgrade should validate in token-exchange authenticated controllers: do not use `params[:shop]` for authorization or data scoping; use the authenticated shop from the verified ID token or session (`current_shopify_session.shop` or JWT `dest` value); and reject requests with `401 Unauthorized` if a `shop` query parameter does not match the authenticated shop. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-63414 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-63414?

Check whether you run shopify_app (RubyGems) or Shopify App at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-63414 · Severity: high · CVSS 4 · Published 2026-10-30

Shopify's shopify_app library is used to authenticate applications that access Shopify stores. A flaw in token-exchange authentication allows an attacker with a valid session for one store to trick the application into operating in the context of a different store, potentially granting unauthorized access to that store's data or enabling unauthorized actions.

Vendors: RubyGems, Shopify.

Quick answers

Is CVE-2026-63414 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-63414 being exploited in the wild.
How severe is CVE-2026-63414?: High severity, with a CVSS score of 4, published 30 October 2026.
Which products and versions are affected?: shopify_app (RubyGems) >= 22.1.0, < 23.0.3, ECOSYSTEM:introduced=22.1.0,fixed=23.0.3; Shopify App before 23.0.3.
Is there a fix for CVE-2026-63414?: Yes. shopify_app (RubyGems): upgrade to 23.0.3 or later. Until then: Applications unable to upgrade should validate in token-exchange authenticated controllers: do not use `params[:shop]` for authorization or data scoping; use the authenticated shop from the verified ID token or session (`current_shopify_session.shop` or JWT `dest` value); and reject requests with `401 Unauthorized` if a `shop` query parameter does not match the authenticated shop. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-63414 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-63414?: Check whether you run shopify_app (RubyGems) or Shopify App at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

shopify_app (RubyGems): upgrade to 23.0.3 or later
```
bundle update shopify_app
```

Applications unable to upgrade should validate in token-exchange authenticated controllers: do not use `params[:shop]` for authorization or data scoping; use the authenticated shop from the verified ID token or session (`current_shopify_session.shop` or JWT `dest` value); and reject requests with `401 Unauthorized` if a `shop` query parameter does not match the authenticated shop.

Technical details

The vulnerability exists in token-exchange authenticated controllers where `current_shopify_domain` could incorrectly resolve to a sanitized `shop` query parameter instead of the authenticated shop identity from the verified ID token or session. An attacker with a valid token for shop A can submit a request with a different `shop` query parameter for shop B, and if the application uses `current_shopify_domain` or `params[:shop]` for authorization or tenant decisions, it will operate in shop B's context. The patch ensures `current_shopify_domain` resolves to the authenticated shop, introduces `authenticated_shopify_domain` for the trusted shop, and rejects mismatched shop parameters with 401 Unauthorized.

Affected products

Shopify shopify_app before 23.0.3

Identifiers

CVE-2026-63414
GHSA-6j52-38f8-qhxr

Timeline

2026-10-29: disclosed

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.