Download the PHP package disrex/stylesmuggler-adobe-patches without Composer

On this page you can find all versions of the php package disrex/stylesmuggler-adobe-patches. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package stylesmuggler-adobe-patches

disrex/stylesmuggler-adobe-patches

A Composer plugin that applies Adobe's official APSB26-146 fix (CVE-2026-75650, internal reference VULN-39341) for the StyleSmuggler zero-day to Magento Open Source and Mage-OS, automatically, detecting your installed version.

It patches the installed packages itself on install and update. It does not rely on cweagans/composer-patches or a root enable-patching flag, so it cannot silently do nothing the way a dependency patch does on composer-patches v1.

Prefer a release that already contains the fix. If you can move to a Magento or Mage-OS release that ships APSB26-146, do that. This plugin is for a store that must patch in place.

Install

You must allow the plugin, or nothing is patched. Because this is a Composer plugin, Composer 2.2 and later ask:

Answer y. If you answer n, or run non-interactively (CI, --no-interaction) without allowing it first, Composer skips the plugin and your store is not patched. To allow it ahead of time (required for CI and deploys), add this to your root composer.json before installing:

On the next composer install or composer update the plugin applies the patch and prints what it did:

What it does

On post-install-cmd and post-update-cmd it:

  1. Detects the store: magento/product-community-edition (Magento) or mage-os/product-community-edition (Mage-OS), falling back to magento/framework.
  2. Picks the patch set for your Magento line (2.4.4 through 2.4.9). If your exact version has no set, it tries the closest one rather than giving up.
  3. Applies Adobe's patch to framework, module-backend, module-email, module-newsletter and the error-report processor, under the right vendor (magento/ or mage-os/).

It is idempotent: an already-patched store reports already applied and nothing changes.

Safe by construction

Coverage

Adobe's patch is built per Magento patch level; this plugin ships all of them and picks by your version. Verified end to end on Magento 2.4.8, and the framework patch verified against Mage-OS framework 2.3.0 (Magento 2.4.8-p5) and 3.4.0 (Magento 2.4.9). Other patch levels rely on patch's strictness: they apply where the files are unchanged and report a mismatch otherwise.

Magento line Adobe patch built against
2.4.4 2.4.4-p18
2.4.5 2.4.5-p17
2.4.6 2.4.6-p15
2.4.7 2.4.7-p10
2.4.8 2.4.8-p5
2.4.9 2.4.9

Mage-OS lines map to these by the Magento version they track.

Remove once you upgrade

This stops re-applying the patch. It does not revert files already patched; move to a release that contains the fix and reinstall to get clean vendor files.

After patching a store that was exposed

Patching shuts the door; it does not evict an attacker who already got in or invalidate secrets they read. If you found any indicator of compromise, rotate the encryption key, database and admin credentials, API tokens and payment-gateway keys, and work through the cleanup guide in the mitigation repo.

Credits and license

The fix is Adobe's (APSB26-146). The patch files under patches/ are Adobe's VULN-39341, repackaged for per-package application by yellowteak. Discovery and the original advisory belong to Sansec. This plugin's own code is MIT; the patch content under patches/ is Adobe's, not covered by that license.


All versions of stylesmuggler-adobe-patches with dependencies

PHP Build Version
Package Version
Requires composer-plugin-api Version ^2.0
php Version >=7.4
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package disrex/stylesmuggler-adobe-patches contains the following files

Loading the files please wait ...