CVE-2026-48356: Adobe Commerce and Magento Unrestricted Upload of File with Dangerous Type Vulnerability
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
Adobe Commerce is affected by an Unrestricted Upload of File with Dangerous Type vulnerability that could result in arbitrary code execution in the context of the current user, potentially gaining elevated access or control over the victim’s account or session. Exploitation of this issue requires user interaction in that a victim must visit a maliciously crafted URL or interact with a compromised web page. Scope is changed.
Description quoted from the CVE record (assigned by adobe, published 2026-07-14).
Weakness: Unrestricted Upload of File with Dangerous Type (CWE-434)
How it can be exploited
Exploitable over the network with low attack complexity needing no privileges and a user must take an action. Impact: confidentiality high, integrity high, availability none. CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
CISA assessment (SSVC): CISA assesses exploitation as active. Automatable: no. Technical impact: total.
- On CISA KEV since
- 2026-10-27
- US federal deadline
- 2026-11-10
- Ransomware use
- Not known
Public exploit evidence (Exploit Observer)
Also known as: BDU:2026-10045, EUVD-2026-44420, GHSA-p3ch-8535-fp8j
VEDAS cluster: VEDAS:GARNETGLIMMER
Exploit Observer links 2 pieces of public exploit code or detection modules that name this CVE or one of its aliases.
Exploit code and modules (2)
Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.
- Code repository: https://github.com/abraxas/cve-2026-48356
- Code repository: https://github.com/piecar21/cve-2026-48356
Research and write-ups (1)
- Research or write-up: https://phpscientist.com/blog/magento-polyshell-cve-2026-48356
Vulnerability databases and vendor advisories (4)
Catalogue entries, not exploit evidence.
- Vulnerability database or vendor advisory: https://euvd.enisa.europa.eu/enisa/EUVD-2026-44420
- Vulnerability database or vendor advisory: https://github.com/advisories/GHSA-p3ch-8535-fp8j
- Vulnerability database or vendor advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-48356
- Vulnerability database or vendor advisory: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-48356
90 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.
VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.
Live scores
- EPSS
- 0.446
likely to be attacked soon - VEDAS
- 0.980
strong exploit evidence - On CISA KEV
- Yes, since 2026-10-27
- Detection rule
- None yet
Thin horizontal line: the “likely” (EPSS 0.10) or “strong” (VEDAS 0.90) threshold. Shaded “no data” areas are periods when cve-scores did not publish. The vertical line is the day CISA added it to its exploited list.
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| Adobe Adobe Commerce | up to and including 2.4.9, 2.4.8-p5, 2.4.7-p10, 2.4.6-p15, 2.4.5-p17, 2.4.4-p18 | 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 is not affected |
| Adobe Adobe Commerce B2B | up to and including 1.5.3, 1.5.2-p5, 1.4.2-p10, 1.3.4-p17, 1.3.3-p18 | 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 is not affected |
| Adobe Magento Open Source | up to and including 2.4.9, 2.4.8-p5, 2.4.7-p10, 2.4.6-p15 | 2.4.9-2026-jul, 2.4.8-2026-jul, 2.4.7-2026-jul, 2.4.6-2026-jul is not affected |
| Adobe Adobe Commerce Events | up to and including 1.20.0 | 1.21.0 is not affected |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
Exploit Observer also maps it to: adobe commerce, adobe commerce_b2b, adobe i\/o_events, adobe magento, adobe_systems_inc. adobe_commerce, adobe_systems_inc. adobe_commerce_b2b, adobe_systems_inc. adobe_commerce_events, adobe_systems_inc. magento_open_source.
How to fix it
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.
Vendor guidance:
- https://helpx.adobe.com/security/products/magento/apsb26-73.html (vendor-advisory)
How to detect it
There is no open VEDAS detection rule for this bug yet. It is listed on the detection gaps page if CISA has confirmed attacks.
References
Vendor advisories and patches
- https://helpx.adobe.com/security/products/magento/apsb26-73.html (vendor-advisory)
Exploits and technical analysis
- https://sansec.io/research/magento-cms-block-loader-deepveindrilling#indicators-of-compromise (third-party-advisory)
- https://sansec.io/research/polyshell-mass-attack-wave (third-party-advisory)
Government sources
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-48356 (government-resource)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, CISA KEV, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.