Affects Adobe Commerce (Magento), a widely used e‑commerce platform; stored XSS enables session takeover across many storefronts; high impact.
CVE-2026-21311
Stored XSS in Adobe Commerce enables session hijacking via vulnerable fields.
Is CVE-2026-21311 being exploited?
Not confirmed. CVE-2026-21311 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.30% probability of exploitation in the next 30 days.
How severe is CVE-2026-21311?
CVE-2026-21311 is rated High with a CVSS score of 8.0. 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-21311?
Yes. A fix has been recorded for CVE-2026-21311. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-21311 affect?
CVE-2026-21311 affects Adobe Commerce/Magento 2.x up to 2.4.9-alpha3, 2.4.8-p3, 2.4.7-p8, 2.4.6-p13, 2.4.5-p15, 2.4.4-p16 and earlier. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-21311?
Upgrade to patched release; apply vendor security update; sanitize inputs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Stored XSS allows attacker to inject JS in victims' browsers, hijacking sessions and potentially data leakage; exploitation requires user interaction.
Patch when possible
- affected<= 2.4.9-alpha3, 2.4.8-p3, 2.4.7-p8, 2.4.6-p13, 2.4.5-p15, 2.4.4-p16
- affected<= 1.5.3-alpha3, 1.5.2-p3, 1.4.2-p8, 1.3.5-p13, 1.3.4-p15, 1.3.3-p16
- affected<= 2.4.9-alpha3, 2.4.8-p3, 2.4.7-p8, 2.4.6-p13, 2.4.5-p15
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.