PatchSiren cyber security CVE debrief
CVE-2026-44472 saleor CVE debrief
CVE-2026-44472 Saleor account activation issue allows attackers to access victim's order history and personal data via email verification exploit. The vulnerability exists in Saleor versions 2.10.0rc1 through 3.21.66, 3.22.62, and 3.23.21, enabling attackers to create an account with a victim's email address and access their order history and personal data if the victim follows the activation link. Defenders should verify exposure and apply patches or compensating controls to prevent unauthorized account merging.
- Vendor
- saleor
- Product
- Unknown
- CVSS
- HIGH 8.1
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-18
- Original CVE updated
- 2026-09-18
- Advisory published
- 2026-08-18
- Advisory updated
- 2026-09-18
Who should care
Defenders responsible for e-commerce platforms using Saleor, particularly those using versions 2.10.0rc1 through 3.21.66, 3.22.62, and 3.23.21, should assess exposure and apply patches or compensating controls.
Why it matters
The Saleor account activation flow vulnerability allows attackers to access victim's order history and personal data via email verification exploit, requiring defenders to verify exposure and apply patches or compensating controls.
- Attackers can access victim's order history and personal data, including names, addresses, and phone numbers
- Victim's account can be compromised without requiring the account password or another authentication factor
- Defenders need to verify exposure and apply patches or compensating controls to prevent unauthorized account merging
- Incident response may be required to address potential data breaches
Technical summary
The Saleor e-commerce platform has a vulnerability in its account activation flow, allowing attackers to create an account with a victim's email address and access their order history and personal data if the victim follows the activation link. The vulnerability exists in Saleor versions 2.10.0rc1 through 3.21.66, 3.22.62, and 3.23.21. The patched supported lines disable automatic merging by default, while the redesigned 3.24.0 flow requires password confirmation before anonymous objects are linked. Defenders should prioritize verifying exposure for e-commerce platforms using Saleor versions 2.10.0rc1 through 3.21.66, 3.22.62, and 3.23.21, and apply patches or compensating controls to prevent unauthorized
Defensive priority
Defenders should prioritize verifying exposure for e-commerce platforms using Saleor versions 2.10.0rc1 through 3.21.66, 3.22.62, and 3.23.21, and apply patches or compensating controls to prevent unauthorized account merging.
Recommended defensive actions
- Verify exposure for e-commerce platforms using Saleor versions 2.10.0rc1 through 3.21.66, 3.22.62, and 3.23.21
- Apply patches or compensating controls to prevent unauthorized account merging
- Monitor for suspicious account activation and order history access attempts
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE record and source references provide details on the Saleor account activation flow vulnerability, including affected versions and fixed releases. The vulnerability allows attackers to access victim's order history and personal data via email verification exploit. Defenders should verify exposure for e-commerce platforms using Saleor versions 2.10.0rc1 through 3.21.66, 3.22.62, and 3.23.21, and apply patches or compensating controls to prevent unauthorized account merging. The patched supported lines disable automatic merging,
Sources and references
Verified primary and authoritative sources
-
CVE-2026-44472 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-44472
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-44472 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-44472
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/saleor/saleor/commit/299cdfb1a5737108b78b5c2c0d29b94f3b7331a2
-
Source reference
Unverified legacy reference
URL: https://github.com/saleor/saleor/commit/42516727823cb74cb6b875070956debecf9ffdb8
-
Source reference
Unverified legacy reference
URL: https://github.com/saleor/saleor/commit/5110542c164991384fa3c4f01983e8c76823ce0f
-
Source reference
Unverified legacy reference
URL: https://github.com/saleor/saleor/commit/dc63e422afc9f6ce115d75f045886b01b4f13e2b
-
Source reference
Unverified legacy reference
URL: https://github.com/saleor/saleor/releases/tag/3.21.67
-
Source reference
Unverified legacy reference
URL: https://github.com/saleor/saleor/releases/tag/3.22.63
-
Source reference
Unverified legacy reference
URL: https://github.com/saleor/saleor/releases/tag/3.23.22
-
Source reference
Unverified legacy reference
URL: https://github.com/saleor/saleor/security/advisories/GHSA-6whj-8p3f-2xqp
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.