# CVE-2026-128046: OpenMage magento-lts 20.17.0 before 20.18.2 Unrestricted File Upload RCE via Custom Options


- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 13 Nov 2026
- **Also known as:** GHSA-4fxg-469f-r6fc, GHSA-r74m-vw7m-pr6g

## What is CVE-2026-128046?

CVE-2026-128046 is a critical vulnerability in OpenMage magento-lts, published on 13 Nov 2026. 

### Official description

OpenMage magento-lts 20.17.0 before 20.18.2 and 21.0.0-beta1 before 21.0.0-beta3 contains an unrestricted file upload vulnerability because the general/file/protected_extensions blocklist omits phar, php8, and phps. Unauthenticated attackers can upload a .phar file through a product File custom option to a predictable media/custom_options path and request it directly to execute code on servers that map .phar to PHP and serve that directory.

Weakness: CWE-184 (Incomplete List of Disallowed Inputs)

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


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

No fix has been published for CVE-2026-128046 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-128046 being exploited?

There is no known exploitation of CVE-2026-128046 in the wild and no public exploit code.

Public exploit code:

- CVE-2026-128046 PoC: OpenMage LTS protected_extensions omits phar/php8/phps - an unauthenticated guest uploads a .phar through a product File custom option and executes it by fetching its predictable media path. Differential lab on v20.18.0 vs v20.18.2 source builds behind a .phar-mapped web tier. (github_poc): https://github.com/googlesky/CVE-2026-128046

## Fix prompt for AI coding agents

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

What it is: CVE-2026-128046 is a critical vulnerability in OpenMage magento-lts, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-128046 in the wild and no public exploit code.

Affected product: OpenMage magento-lts. 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-128046/ (Markdown: https://insights.sbomify.com/CVE-2026-128046/index.md)
```

## Sources

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

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