CVE-2026-44472

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (48th 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
8.1EG
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.6%CVSS: 8.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Saleor is an e-commerce platform. From 2.10.0rc1 until 3.21.67, 3.22.63, and 3.23.22, the account activation flow treats email verification as sufficient proof of account ownership and automatically associates anonymous commerce data with the newly activated account. An attacker can use accountRegister to create an account with a victim's email address before the victim registers. If the victim follows the activation link sent to that mailbox, Saleor activates the attacker-created account and saleor/graphql/account/mutations/account/confirm_account.py can merge anonymous orders and gift-card data for the same email address without requiring the account password or another authentication factor. The attacker can then access the merged order history and personal data, including names, addresses, and phone numbers. The patched supported lines disable automatic merging by default, while the redesigned 3.24.0 flow requires password confirmation before anonymous objects are linked. This issue is fixed in versions 3.21.67, 3.22.63, and 3.23.22.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
The EG Score, 8.1 of 10.
Exploitation0.6% × 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.6%
EPSS %ILE
48th
KEV
Not listed

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.

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

August 18, 2026

Last Modified

September 18, 2026

Advisory Details (8)

Auto-updated Aug 18, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available

3.23.22

Patch available: saleor/saleor 3.23.22

https://github.com/saleor/saleor/releases/tag/3.23.22
GitHub release Patch Available

3.22.63

Patch available: saleor/saleor 3.22.63

https://github.com/saleor/saleor/releases/tag/3.22.63
GitHub release Patch Available

3.21.67

Patch available: saleor/saleor 3.21.67

https://github.com/saleor/saleor/releases/tag/3.21.67
GitHub commit Patch Available

commit dc63e422afc9 (saleor/saleor)

Patch available: saleor/saleor 3.21.67 (contains commit dc63e422afc9)

https://github.com/saleor/saleor/commit/dc63e422afc9f6ce115d75f045886b01b4f13e2b
GitHub commit

commit 5110542c1649 (saleor/saleor)

Fix landed in saleor/saleor commit 5110542c1649 — awaiting tagged release

https://github.com/saleor/saleor/commit/5110542c164991384fa3c4f01983e8c76823ce0f
GitHub commit Patch Available

commit 42516727823c (saleor/saleor)

Patch available: saleor/saleor 3.23.22 (contains commit 42516727823c)

https://github.com/saleor/saleor/commit/42516727823cb74cb6b875070956debecf9ffdb8
GitHub commit Patch Available

commit 299cdfb1a573 (saleor/saleor)

Patch available: saleor/saleor 3.22.63 (contains commit 299cdfb1a573)

https://github.com/saleor/saleor/commit/299cdfb1a5737108b78b5c2c0d29b94f3b7331a2
GitHub advisoryMentions a patch (unverified)

Account pre-hijacking vulnerability due to unverified anonymous order merge · Advisory · saleor/saleor · GitHub

https://github.com/saleor/saleor/security/advisories/GHSA-6whj-8p3f-2xqp

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 47× 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 it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 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). Most recent first.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  3. 2026-10-12 16:05 UTCEG score recompute
  4. 2026-10-11 19:47 UTCEG score recompute
  5. 2026-10-11 17:01 UTCEG score recompute
  6. 2026-10-11 14:27 UTCEG score recompute
  7. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  10. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  12. 2026-10-06 21:39 UTCEG score recompute
  13. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  14. 2026-10-06 08:22 UTCEG score recompute
  15. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  16. 2026-10-05 09:37 UTCEG score recompute
  17. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  18. 2026-10-03 17:38 UTCEG score recompute
  19. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  20. 2026-10-03 03:00 UTCEG score recompute
  21. 2026-10-02 01:28 UTCEG score recompute
  22. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  23. 2026-09-30 21:38 UTCEG score recompute
  24. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  25. 2026-09-30 09:48 UTCEG score recompute
Show 69 more
  1. 2026-09-28 21:56 UTCEG score recompute
  2. 2026-09-27 21:15 UTCEG score recompute
  3. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  4. 2026-09-27 07:55 UTCEG score recompute
  5. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  6. 2026-09-25 01:26 UTCEG score recompute
  7. 2026-09-23 20:19 UTCEG score recompute
  8. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  9. 2026-09-22 20:25 UTCEG score recompute
  10. 2026-09-22 08:32 UTCEG score recompute
  11. 2026-09-20 21:23 UTCEG score recompute
  12. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  13. 2026-09-19 19:49 UTCEG score recompute
  14. 2026-09-18 20:21 UTCEG score recompute
  15. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  16. 2026-09-18 00:15 UTCEG score recompute
  17. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  18. 2026-09-16 23:24 UTCEG score recompute
  19. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  20. 2026-09-16 11:41 UTCEG score recompute
  21. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  22. 2026-09-15 11:49 UTCEG score recompute
  23. 2026-09-14 00:40 UTCEG score recompute
  24. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  25. 2026-09-13 01:14 UTCEG score recompute
  26. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  27. 2026-09-12 01:48 UTCEG score recompute
  28. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  29. 2026-09-11 14:05 UTCEG score recompute
  30. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  31. 2026-09-10 14:39 UTCEG score recompute
  32. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  33. 2026-09-09 03:25 UTCEG score recompute
  34. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  35. 2026-09-07 16:08 UTCEG score recompute
  36. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  37. 2026-09-06 14:47 UTCEG score recompute
  38. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  39. 2026-09-06 03:05 UTCEG score recompute
  40. 2026-09-04 15:53 UTCEG score recompute
  41. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  42. 2026-09-02 16:49 UTCEG score recompute
  43. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  44. 2026-09-01 14:36 UTCEG score recompute
  45. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  46. 2026-08-31 02:45 UTCEG score recompute
  47. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  48. 2026-08-30 03:18 UTCEG score recompute
  49. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  50. 2026-08-29 03:48 UTCEG score recompute
  51. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  52. 2026-08-28 01:29 UTCEG score recompute
  53. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  54. 2026-08-27 02:03 UTCEG score recompute
  55. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  56. 2026-08-25 14:53 UTCEG score recompute
  57. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  58. 2026-08-24 15:28 UTCEG score recompute
  59. 2026-08-23 04:19 UTCEG score recompute
  60. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  61. 2026-08-22 04:53 UTCEG score recompute
  62. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  63. 2026-08-21 05:24 UTCEG score recompute
  64. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  65. 2026-08-19 18:15 UTCEG score recompute
  66. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  67. 2026-08-18 18:23 UTCEG score recompute
  68. 2026-08-18 17:26 UTCEG score recomputeFirst assessed: 8.1 HIGH
  69. 2026-08-18 17:26 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-44472?
CVE-2026-44472 is a high-severity vulnerability; its CVE record was published on August 18, 2026. Saleor is an e-commerce platform. From 2.10.0rc1 until 3.21.67, 3.22.63, and 3.23.22, the account activation flow treats email verification as sufficient proof of account ownership and automatically associates anonymous commerce data with the newly activated account. An attacker can use…
When was the CVE record for CVE-2026-44472 published?
The CVE record for CVE-2026-44472 was published on August 18, 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 September 18, 2026; the record at its source may have been updated since.
Is CVE-2026-44472 actively exploited?
CVE-2026-44472 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-44472?
CVE-2026-44472 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-44472?
A fix for CVE-2026-44472 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-44472

Explore →

Is Your Infrastructure Affected by CVE-2026-44472?

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

Book a Demo →Browse All CVEs