CVE-2026-63414

HIGHPre-NVD 7.67.6
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (55th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-114553 (ENISA EUVD) · GHSA-6j52-38f8-qhxr (GitHub Security Advisories)Source: ENISA EUVD

7.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Shopify App is a Rails engine for building Shopify applications. From 22.1.0 until 23.0.3, token-exchange authenticated controllers can expose a request-derived shop context instead of the identity from a verified Shopify ID token or active Shopify session. current_shopify_domain can resolve to the sanitized shop query parameter, so a request authenticated for one shop can cause application code to treat a different requested shop as current. Affected applications use shopify_app token-exchange authentication, accept authenticated requests with a shop query parameter, and rely on current_shopify_domain or params[:shop] for authorization, tenant lookup, stored access-token selection or shop-scoped data access. An attacker with a valid Shopify session token for one shop can supply another shop in that parameter and potentially obtain unauthorized application data or perform shop-scoped actions, depending on the application's authorization model. This issue is fixed in version 23.0.3.

CVSS
7.6
EG Score
7.6HIGHmedium confidence
EG Risk
34
EG Risk 34/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)
Severity76% × 45%
Impact severity (EG Severity): CVSS 7.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.8% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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 none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.7%
EPSS %ILE
55th
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.6): severity, escalated by confirmed exploitation. This CVE's 7.6 is its impact severity (EG Severity), not escalated.

EG Severity
7.6 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). 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: 14 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 none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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

October 29, 2026

Last Modified

November 5, 2026

Advisory Details (4)

Auto-updated Oct 30, 2026
Patch available. Sources: github_release, github, github_pr, github_commit.
GitHub release Patch Available

v23.0.3

Patch available: Shopify/shopify_app v23.0.3

https://github.com/Shopify/shopify_app/releases/tag/v23.0.3
GitHub commit Patch Available

commit a09ccc04b955 (Shopify/shopify_app)

Patch available: Shopify/shopify_app v23.0.3 (contains commit a09ccc04b955)

https://github.com/Shopify/shopify_app/commit/a09ccc04b9556cbb31c6d56ed81aeb6b9b6c0756
GitHub pull request Patch Available

Harden token exchange shop context handling

Patch available: Shopify/shopify_app v23.0.3 (PR #2081 merged 2026-06-24)

https://github.com/Shopify/shopify_app/pull/2081
GitHub advisoryMentions a patch (unverified)

Token exchange shop context confusion may allow cross-shop authorization bypass in affected apps · Advisory · Shopify/shopify_app · GitHub

https://github.com/Shopify/shopify_app/security/advisories/GHSA-6j52-38f8-qhxr

Vendor Advisories for CVE-2026-63414(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
rubygemsshopify_app @ 23.0.3 (fixes >= 22.1.0, < 23.0.3)—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)
PackageVulnerable rangeFix by version rangeDependents
shopify_app22.1.0 ... 23.0.2 (12 versions)
  • 22.1.0 up to 23.0.3: fixed in 23.0.3
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 22× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 16:53 UTCEPSS rescoreEPSS 0.7% · 55th percentile
  2. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.7% · 55th percentile
  3. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.7% · 55th percentile
  4. 2026-11-11 03:55 UTCEchelonGraph re-scored
  5. 2026-11-11 03:55 UTCGHSA enrichmentGHSA-6j52-38f8-qhxr · GitHub severity HIGH
  6. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.7% · 55th percentile
  7. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.7% · 55th percentile
  8. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.7% · 55th percentile
  9. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.7% · 55th percentile
  10. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.7% · 55th percentile
  11. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.7% · 55th percentile
  12. 2026-11-05 04:27 UTCEchelonGraph re-scored
  13. 2026-11-05 04:27 UTCGHSA enrichmentGHSA-6j52-38f8-qhxr · GitHub severity HIGH
  14. 2026-11-05 03:19 UTCEchelonGraph re-scored
  15. 2026-11-05 03:19 UTCGHSA enrichmentGHSA-6j52-38f8-qhxr · GitHub severity HIGH
  16. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.5% · 46th percentile
  17. 2026-11-03 20:19 UTCEchelonGraph re-scored
  18. 2026-11-03 20:19 UTCGHSA enrichmentGHSA-6j52-38f8-qhxr · GitHub severity HIGH
  19. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  20. 2026-11-02 19:27 UTCEchelonGraph re-scored
  21. 2026-11-02 19:27 UTCGHSA enrichmentGHSA-6j52-38f8-qhxr · GitHub severity HIGH
  22. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  23. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  24. 2026-11-01 07:41 UTCGHSA enrichmentGHSA-6j52-38f8-qhxr · GitHub severity HIGH
  25. 2026-11-01 07:41 UTCEchelonGraph re-scored
Show 6 more
  1. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  2. 2026-10-31 00:12 UTCENISA EUVD ID recordedEUVD-2026-114553 · Source: ENISA EUVD
  3. 2026-10-30 23:26 UTCEchelonGraph re-scored
  4. 2026-10-30 22:54 UTCEchelonGraph re-scoredFirst assessed: 7.6 HIGH
  5. 2026-10-30 22:53 UTCMITRE cvelistV5CVSS → 7.6 · CVSS v4 → 7.6
  6. 2026-10-29 17:39 UTCEchelonGraph re-scored

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-63414?
CVE-2026-63414 is a high-severity vulnerability; its CVE record was published on October 29, 2026. Shopify App is a Rails engine for building Shopify applications. From 22.1.0 until 23.0.3, token-exchange authenticated controllers can expose a request-derived shop context instead of the identity from a verified Shopify ID token or active Shopify session. current_shopify_domain can resolve to the…
When was the CVE record for CVE-2026-63414 published?
The CVE record for CVE-2026-63414 was published on October 29, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 5, 2026; the record at its source may have been updated since.
Is CVE-2026-63414 actively exploited?
CVE-2026-63414 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (55th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-63414?
CVE-2026-63414 has a CVSS base score of 7.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-63414?
A fix for CVE-2026-63414 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-63414 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-63414

Explore →

Is Your Infrastructure Affected by CVE-2026-63414?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs