Skip to content
Web

CVE-2026-44472

8.1
High
EPSS 0.44%Patch availableAug 19, 2026

Account-activation auth bypass merges anonymous orders into attacker-created Saleor accounts.

common questions

Is CVE-2026-44472 being exploited?

Not confirmed. CVE-2026-44472 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.44% probability of exploitation in the next 30 days.

How severe is CVE-2026-44472?

CVE-2026-44472 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-44472?

Yes. A fix has been recorded for CVE-2026-44472. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-44472 affect?

CVE-2026-44472 affects Saleor e-commerce >=2.10.0rc1 up to (but not including) 3.21.67, 3.22.63, 3.23.22. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-44472?

Upgrade to 3.21.67 / 3.22.63 / 3.23.22 or 3.24.0+; or disable automatic merging until patched.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Saleor e-commerce >=2.10.0rc1 up to (but not including) 3.21.67, 3.22.63, 3.23.22
impact

Attacker pre-registers victim email; if victim clicks activation link, attacker gains access to merged orders, gift-cards and PII (names, addresses, phones) without a password.

action required

Patch when possible

affected versions
saleor saleor
  • affected>= 2.10.0rc1 and < 3.21.67
  • affected>= 3.22.0-a.0 and < 3.22.63
  • affected>= 3.23.0-a.0 and < 3.23.22

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free