Skip to content

WebCritical 9.2Patch available

CVE-2026-128046

Unauthenticated RCE via .phar upload in OpenMage Magento LTS

How scary is it?

updated 14 Nov 2026
  • Yes

    Works without logging in1

    No account and no user action needed (CVSS PR:N, UI:N).

  • Yes

    Reachable over the network1

    Can be attacked remotely (CVSS AV:N).

  • Yes

    Proof-of-concept code is public2

    1 GitHub proof of concept. GitHub proofs of concept are unvetted: some are fake or carry malware. No Exploit-DB entry or Metasploit exploit module on record.

  • None known

    Attacks seen in the wild1

    None reported that we know of. CISA's SSVC assessment says exploitation: none.

  • No

    On CISA's exploited list3

    Not in the catalog as of our last sync.

Scare-o-meter

Act this week

Serious and within reach of attackers. Schedule the fix this week.

  1. Low signal
  2. Routine patch
  3. Act this week
  4. Drop everything

Why: Public proof-of-concept code exists for a network-reachable flaw; CVSS 9.2.1 Read from the same rule that decides our alert emails.

Are you affected? only if all are true

  1. You run OpenMage magento-lts in an affected version>= 20.17.0 and < 20.18.2 / >= 21.0.0-beta1 and < 21.0.0-beta3

    Vendor says fixed in: 20.18.2, 21.0.0-beta3.

    As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.

    See the affected products table · Source 1

  2. An attacker can reach it over the network

    CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.

    Source 1

  3. Specific conditions are met that the attacker does not control

    CVSS attack complexity: High (AC:H). Needs specific conditions, a race or a particular configuration. The CVE record does not always say which.

    Source 1

Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.

What to do

  1. Per the vendorUpgrade to a fixed release20.18.2 / 21.0.0-beta3

    Fixed releases as stated by the vendor in the CVE record.

    See the affected products table · Source 1

  2. Recommendation, AI-writtenUpgrade to 20.18.2+ or 21.0.0-beta3+; block/deny access to media/custom_options until patched

    Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.

Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.

Major vulnerability. Unauthenticated remote code execution in a widely used Magento LTS e‑commerce platform; can lead to full site takeover, data theft, and supply‑chain risk — high impact for any org running Magento.

CVSS
9.2Criticalscored by the publisher (CNA)
Exploited in the wild
Not knownUnvetted proof-of-concept code on GitHub; not in CISA KEV
EPSS
0.80%chance of exploitation in the next 30 daystop 43% of scored CVEsFIRST score of 21 Nov 2026
Fix
Fixed in 20.18.2, 21.0.0-beta3per the vendor
Published
13 Nov 2026analysed here 14 Nov 2026

Do first. Upgrade to a fixed release: 20.18.2, 21.0.0-beta3.

Summary

Impact

Unauthenticated attackers can upload .phar to product custom options and execute PHP on servers mapping .phar — full remote code execution/site takeover.

Triage

Exploitable
At runtime
Attack vector
network
Weakness
Can a WAF block it?
Partly. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

ProductAffected versions
OpenMage magento-lts>= 20.17.0 and < 20.18.2>= 21.0.0-beta1 and < 21.0.0-beta3Vendor says fixed in: 20.18.2, 21.0.0-beta3

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.

Products named in our analysis

  • OpenMage magento-lts 20.17.0 before 20.18.2
  • OpenMage magento-lts 21.0.0-beta1 before 21.0.0-beta3
  • Any Magento instance that maps .phar to PHP and serves media/custom_options

Fix and mitigation

Action required

Immediate action required

WAF and other mitigations

Can a WAF block it? Partly. The attack involves uploading a .phar file via an HTTP request to a specific media/custom_options path. A WAF could detect and block uploads of .phar files, which are unusual for normal users. A custom WAF rule can filter upload of .phar files to media/custom_options endpoint, but attackers can vary the request. No tracked WAF vendor has published a rule for this CVE yet.

What a custom rule would match: upload of .phar files to media/custom_options endpoint

Also consider: patch · custom WAF rule

Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
Unvetted proof-of-concept code on GitHub: 1 GitHub proof of concept
CISA SSVC
exploitation none, automatable no, technical impact totalAssessed by CISA 13 Nov 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

GitHub proofs of concept

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 13 Nov 2026Published
  2. 13 Nov 2026CISA SSVC assessment: exploitation nonesame day later
  3. 13 Nov 2026CVE record last updatedsame day later
  4. 14 Nov 2026First proof-of-concept repository on GitHub (unvetted)same day later
  5. 14 Nov 2026Analysed by vulneraibility.com1 day later

Common questions

Is CVE-2026-128046 being exploited?

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

How severe is CVE-2026-128046?

CVE-2026-128046 is rated Critical with a CVSS score of 9.2. 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-128046?

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

What does CVE-2026-128046 affect?

CVE-2026-128046 affects OpenMage magento-lts 20.17.0 before 20.18.2, OpenMage magento-lts 21.0.0-beta1 before 21.0.0-beta3, Any Magento instance that maps .phar to PHP and serves media/custom_options. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-128046?

Upgrade to 20.18.2+ or 21.0.0-beta3+; block/deny access to media/custom_options until patched

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

References

NVDCVE.orgCVE DetailsSource

5 references in the CVE record, grouped by the tags the record gives them.

Advisories (2)

  • github.com /OpenMage/magento-lts/security/advisories/GHSA-4fxg-469f-r6fc
  • vulncheck.com /advisories/openmage-magento-lts-20.17.0-before-20.18.2-unrestricted-file-upload

Patches (3)

  • github.com /OpenMage/magento-lts/commit/ba76b2346fe1e380f39c23e68ccb818d7324d24f
  • github.com /OpenMage/magento-lts/commit/5b6f985785245a964aa3dc78609f6af44d9d5e27
  • github.com /OpenMage/magento-lts/commit/dd692b825ba50f196bcc20ae67fbed48dd95da56

Also tracked as GHSA-4fxg-469f-r6fc (OSV).

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.