(CVE-2026-96377)
Vulnerability from drupal – Published: 2026-09-23 17:21 – Updated: 2026-09-23 17:30 – Source websiteThis 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.
| URL | Type | |
|---|---|---|
{
"affected": [
{
"database_specific": {
"affected_versions": "\u003c1.0.7"
},
"package": {
"ecosystem": "Packagist:https://packages.drupal.org/8",
"name": "drupal/combined_image_style"
},
"ranges": [
{
"database_specific": {
"constraint": "\u003c1.0.7"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1.0.7"
}
],
"type": "ECOSYSTEM"
}
],
"severity": []
}
],
"aliases": [
"CVE-2026-96377"
],
"credits": [
{
"contact": [
"https://www.drupal.org/u/svendecabooter"
],
"name": "Sven Decabooter (svendecabooter)"
}
],
"details": "This module enables you to combine multiple image styles into a single image derivative.\n\nThe 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.\n\nSites are affected simply by having the module installed, even when no combined image styles are configured or in use.\n\nThis vulnerability is mitigated by the fact that only public files can be targeted, and derivatives of private files are still protected by core\u0027s token check.",
"id": "DRUPAL-CONTRIB-2026-188",
"modified": "2026-09-23T17:30:51.000Z",
"published": "2026-09-23T17:21:51.000Z",
"references": [
{
"type": "WEB",
"url": "https://www.drupal.org/sa-contrib-2026-188"
}
],
"schema_version": "1.7.0"
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.