CVE-2026-118571: Media alias display · This module allows for direct viewing of a file with the URL alias
Affects drupal/media_alias_displaySource GCVE Database
Not known to be exploited : upgrade to 3.0.3 or 2.1.3 when convenient.
Data as of 28 Oct 2026, 20:30 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- Patch
- Available – fixed in 3.0.3, 2.1.3
Exploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade drupal/media_alias_display to 3.0.3 or 2.1.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Packagist https //packages.drupal.org/8drupal/media_alias_display | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Apply the official fixes by upgrading to media_alias_display versions 2.1.3 or later and 3.0.3 or later. Additionally, ensure Drupal is configured to handle non-public files using a custom or contributed module that provides an additional file scheme to prevent improper caching. No further action is required beyond applying these patches and configuration changes.
Description
The Media alias display module in Drupal allows direct viewing of files via URL aliases, which can cause files to be served with a 'Cache-Control: public' header when they should not be cacheable. This may result in some users receiving cached versions of files containing information they should not access. The vulnerability is a follow-up to a previous advisory and is mitigated by proper Drupal configuration for non-public files and the requirement that an attacker must know to request a previously cached file accessed by a more privileged user.