CVE-2026-48356: Adobe Commerce / Magento unrestricted file upload (APSB26-73)

Exploited in the wild Critical 9.3 EPSS 44.6% Magento / Adobe Commerce

Adobe Commerce and Magento Open Source accept upload of files with a dangerous type, which Adobe rates critical (CVSS 9.6) and says can lead to arbitrary code execution; no authentication is required but a victim must open a crafted URL or page. It was fixed in the July 14, 2026 security update APSB26-73. CISA added it to the Known Exploited Vulnerabilities catalog on 2026-10-27, so it is being exploited in the wild.

CVE-2026-48356CVE identifier
9.3CVSS 3.1 base score (critical)
2026-10-27added to CISA's exploited list (US federal deadline 2026-11-10)
44.6%EPSS: chance of exploitation in the next 30 days (higher than 99% of CVEs)
2026-07-14published

What do these terms mean? CVE · CVSS score · exploited (KEV) · EPSS · backported fix · all terms

What to do now

Check whether you run Magento / Adobe Commerce and which version (commands below).
Install the fixed version for your system: see “Patch it” below.
Flush the Magento cache after applying the patch (Admin > System > Cache Management or bin/magento cache:flush). On Adobe Commerce on Cloud, commit the patch into m2-hotfixes/ and redeploy.
If you cannot patch today, apply the temporary mitigation below and patch as soon as possible.
Because this flaw is being exploited, also check the server for signs of compromise.

Affected and fixed versions

Affected:

Adobe Commerce 2.4.9, 2.4.8-p5 and earlier, 2.4.7-p10 and earlier, 2.4.6-p15 and earlier, 2.4.5-p17 and earlier, 2.4.4-p18 and earlier
Adobe Commerce B2B 1.5.3, 1.5.2-p5 and earlier, 1.4.2-p10 and earlier, 1.3.4-p17 and earlier, 1.3.3-p18 and earlier
Magento Open Source 2.4.9, 2.4.8-p5 and earlier, 2.4.7-p10 and earlier, 2.4.6-p15 and earlier
Adobe Commerce Events 1.6.0 to 1.20.0

Fixed in:

Adobe Commerce 2.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 Commerce B2B 1.5.3-2026-jul, 1.5.2-2026-jul, 1.4.2-2026-jul, 1.3.4-2026-jul, 1.3.3-2026-jul
Magento Open Source 2.4.9-2026-jul, 2.4.8-2026-jul, 2.4.7-2026-jul, 2.4.6-2026-jul
Adobe Commerce Events 1.21.0

Am I affected?

php bin/magento --version
php vendor/bin/patch-status

Patch it

Use the commands for your system. Distribution packages often keep an older version number with the fix backported, so compare with the fixed package versions in the table below, not only with the upstream version.

Debian

not packaged: composer require magento/product-community-edition

Ubuntu

not packaged: composer

RHEL, AlmaLinux, Rocky, Oracle

not packaged: composer

Fedora

not packaged

SUSE / openSUSE

not packaged

Amazon Linux

not packaged: composer

Arch Linux

not packaged

Alpine

not packaged

FreeBSD

not packaged

Built from source

# Adobe ships the July 2026 fix as Isolated patch files (no Composer packages).
# 1. Be on the latest -p release of your line (2.4.9, 2.4.8-p5, 2.4.7-p10, 2.4.6-p15, 2.4.5-p17, 2.4.4-p18).
# 2. Download the matching 2-4-x-...-jul-2026.zip from Adobe KB ka-37421 and unzip it in the Magento root.
# 3. Apply each component file (CE first, then EE, then B2B):
cd /path/to/magento
patch -p1 < 246p15-2026-07-001-CE.patch   # example file name for 2.4.6-p15
# 4. Refresh caches, then confirm with the Commerce Version Tool:
php bin/magento cache:flush
php vendor/bin/patch-status

General update steps for every system are on the Linux and Unix & BSD pages; after updating, see which services to restart.

If you cannot patch yet

Adobe Commerce on Cloud: copy the patch file(s) into the m2-hotfixes/ directory, commit and push; the fix is also included in the latest Magento Cloud Patches release.

CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

https://www.adobe.com/trust/security/products/commerce/apsb26-73.html ; ; BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk ; Forensics Triage Requirements: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk ; https://nvd.nist.gov/vuln/detail/CVE-2026-48356

Related vulnerabilities

Sources

Page generated automatically from official sources on 2026-11-03 17:06 UTC and reviewed by an editor. Always confirm with your vendor's advisory.