Skip to content
major vulnerability· requires attention

Critical RCE in Adobe Commerce, a widely deployed e‑commerce platform; no user interaction required and high potential for broad compromise and business disruption.

Applications

CVE-2026-48358

CRITICAL
Critical
EPSS 1%Patch availableJul 15, 2026

Remote code execution in Adobe Commerce via improper output encoding; no user interaction needed

common questions

Is CVE-2026-48358 being exploited?

Not confirmed. CVE-2026-48358 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 1.5% probability of exploitation in the next 30 days.

How severe is CVE-2026-48358?

CVE-2026-48358 is rated Critical. 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-48358?

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

What does CVE-2026-48358 affect?

CVE-2026-48358 affects Adobe Commerce (Magento) installations, Magento Open Source. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-48358?

Apply vendor patch immediately; restrict admin interfaces, deploy WAF rules, and monitor logs.

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

executive summary
technical analysis
affected
Adobe Commerce (Magento) installationsMagento Open Source
impact

Remote code execution in app context without user interaction; attackers can run arbitrary code, modify/steal data, deploy webshells, and pivot to internal systems.

action required

Immediate action required

affected versions
Adobe Adobe Commerce
  • affected<= 2.4.9, 2.4.8-p5, 2.4.7-p10, 2.4.6-p15, 2.4.5-p17, 2.4.4-p18
vendor says fixed in2.4.9-2026-jul, 2.4.8-2026-jul, 2.4.7-2026-jul, 2.4.6-2026-jul, 2.4.5-2026-jul, 2.4.4-2026-jul
Adobe Adobe Commerce B2B
  • affected<= 1.5.3, 1.5.2-p5, 1.4.2-p10, 1.3.4-p17, 1.3.3-p18
vendor says fixed in1.5.3-2026-jul, 1.5.2-2026-jul, 1.4.2-2026-jul, 1.3.4-2026-jul, 1.3.3-2026-jul
Adobe Adobe Commerce Events
  • affected<= 1.20.0
vendor says fixed in1.21.0
Adobe Magento Open Source
  • affected<= 2.4.9, 2.4.8-p5, 2.4.7-p10, 2.4.6-p15
vendor says fixed in2.4.9-2026-jul, 2.4.8-2026-jul, 2.4.7-2026-jul, 2.4.6-2026-jul

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