# CVE-2026-48356: Adobe Commerce and Magento Unrestricted Upload of File with Dangerous Type

> Attackers can upload malicious files to Adobe Commerce to execute arbitrary code and take over accounts, requiring user interaction.

- **Severity:** Critical 9.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Yes, since 27 Oct 2026 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Jul 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-p3ch-8535-fp8j

## What is CVE-2026-48356?

CVE-2026-48356 is a critical vulnerability in Adobe Commerce, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2026-48356?

It affects 4 products.


Products: Adobe Commerce, Adobe Commerce B2b, Adobe I\/O Events, Adobe Magento.

## How do I fix CVE-2026-48356?

No fix has been published for CVE-2026-48356 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 10 Nov 2026.

## Is CVE-2026-48356 being exploited?

Yes. Attackers have exploited CVE-2026-48356 in the wild since at least 27 Oct 2026.

Public exploit code:

- CVE-2026-48356 - Magento Open Source - Critical 9.3 - Unauthenticated POST /rest/default/V1/guest-carts/{cartId}/items - Unauthenticated Unrestricted File Upload (PolyShell) (github_poc): https://github.com/abraxas/CVE-2026-48356

## Other vulnerabilities in Adobe Commerce

- [CVE-2026-75650](https://insights.sbomify.com/CVE-2026-75650/): Adobe Commerce and Magento Improper Neutralization of Special Elements Used in a Template Engine (critical 10.0, exploited in the wild)
- [CVE-2024-34102](https://insights.sbomify.com/CVE-2024-34102/): Adobe Commerce and Magento Open Source Improper Restriction of XML External Entity Reference (XXE) (critical 9.8, exploited in the wild)
- [CVE-2022-24086](https://insights.sbomify.com/CVE-2022-24086/): Adobe Commerce and Magento Open Source Improper Input Validation (critical 9.8, exploited in the wild)
- [CVE-2026-71362](https://insights.sbomify.com/CVE-2026-71362/): Adobe Commerce and Magento Incorrect Authorization Vulnerability (critical 9.1, exploited in the wild)
- [CVE-2025-54236](https://insights.sbomify.com/CVE-2025-54236/): Adobe Commerce and Magento Improper Input Validation (critical 9.1, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48356 and fix it if it is affected.

What it is: CVE-2026-48356 is a critical vulnerability in Adobe Commerce, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2026-48356 in the wild since at least 27 Oct 2026.

Affected product: Adobe Commerce. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48356/ (Markdown: https://insights.sbomify.com/CVE-2026-48356/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48356
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48356
- OSV: https://osv.dev/vulnerability/CVE-2026-48356

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48356/
Summaries are generated and may contain mistakes; the official description above is the record.