PatchClock

PHP security digest · 23 Sep 2026

This module enables you to combine multiple image styles into a single image derivative. The module does not sufficiently validate image style names when gener...

Unrated CVE-2026-96377

Package
drupal/combined_image_style
Fixed in
1.0.7
Published
Wed 23 Sep 2026, 18:21 LisbonUpdated Mon 26 Oct 2026, 02:25 Lisbon

In plain words

The module does not sufficiently validate image style names when generating image derivatives. Under certain circumstances, anonymous users can generate derivatives without a valid token, potentially causing a denial of service. Sites are affected simply by having the module installed, even if no combined image styles are configured or used. Only public files can be targeted; derivatives of private files remain protected by core's token check.

Am I affected?

Look for drupal/combined_image_style and its installed version in composer.lock. The advisory lists 1.0.7 as fixed but gives no affected version range. Having the module installed is enough for exposure, so do not rule your site out because combined image styles are unused or unconfigured.

What to do

Check which version you have, then update to a fixed release for your branch (1.0.7):

composer show drupal/combined_image_style | grep versions
composer update drupal/combined_image_style

If your version constraint in composer.json keeps you below a fixed release, raise it first. Whether your configuration is affected, and the exact version ranges, are in the advisory itself.

If you cannot update yet

Only public files can be targeted. Derivatives of private files remain protected by core's token check.

The advisory's description

This module enables you to combine multiple image styles into a single image derivative.

The module does not sufficiently validate image style names when generating image derivatives. Under certain circumstances, this allows anonymous users to generate image derivatives without a valid token, potentially leading to a denial of service.

Sites are affected simply by having the module installed, even when no combined image styles are configured or in use.

This vulnerability is mitigated by the fact that only public files can be targeted, and derivatives of private files are still protected by core's token check.

The advisory

From OSV.dev, which gathers the GitHub Advisory Database, FriendsOfPHP and Drupal security advisories; the summary is theirs. The description is OSV's record of the advisory. "In plain words", "Am I affected?" and "If you cannot update yet" are based on that advisory, and checked to name no version it does not.