- Security-news - lists.drupal.org

Flag attendance field - Critical - PHP object injection - SA-CONTRIB-2026-049
by security-news＠drupal.org 17 Jun '26

17 Jun '26

View online: https://www.drupal.org/sa-contrib-2026-049 Project: Flag attendance field [1] Date: 2026-June-17 Security risk: *Critical* 19 ∕ 25 AC:None/A:User/CI:All/II:All/E:Theoretical/TD:Default [2] Vulnerability: PHP object injection Affected versions: <1.2 CVE IDs: CVE-2026-55809 Description: The Flag attendance field module gives you the ability to add attendance by depending on Flag module [3]. flag_attendance_field stores some data as PHP-serialized strings. In some situations, malicious data can be written directly to the field. This can lead to an object injection vulnerability when the data are unserialized. This vulnerability is mitigated by the fact that an attacker must have permission to edit a content entity with an attached flag_attendance_field field. In addition, the core JSON:API module must be enabled with the option "Accept all JSON:API create, read, update, and delete operations", which is not the default, or the attacker needs some other way to edit field values directly. Solution: Install the latest version: * If you use the Flag attendance field module for Drupal, upgrade to Flag attendance field 8.x-1.2 [4]. Reported By: * Drew Webber (mcdruid) [5] of the Drupal Security Team Fixed By: * Anas Mawlawi (anas_maw) [6] * Benji Fisher (benjifisher) [7] of the Drupal Security Team * Drew Webber (mcdruid) [8] of the Drupal Security Team Coordinated By: * Benji Fisher (benjifisher) [9] of the Drupal Security Team * Drew Webber (mcdruid) [10] of the Drupal Security Team * Jess (xjm) [11] of the Drupal Security Team Security issue: https://git.drupalcode.org/security/185193-flag_attendance_field-security/-… [12] ------------------------------------------------------------------------------ Contribution record [13] [1] https://www.drupal.org/project/flag_attendance_field [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/flag [4] https://www.drupal.org/project/flag_attendance_field/releases/8.x-1.2 [5] https://www.drupal.org/u/mcdruid [6] https://www.drupal.org/u/anas_maw [7] https://www.drupal.org/u/benjifisher [8] https://www.drupal.org/u/mcdruid [9] https://www.drupal.org/u/benjifisher [10] https://www.drupal.org/u/mcdruid [11] https://www.drupal.org/u/xjm [12] https://git.drupalcode.org/security/185193-flag_attendance_field-security/-… [13] https://new.drupal.org/contribution-record?source_link=https%3A//www.drupal…

1 0

Formatter Field - Critical - PHP object injection - SA-CONTRIB-2026-048
by security-news＠drupal.org 17 Jun '26

17 Jun '26

View online: https://www.drupal.org/sa-contrib-2026-048 Project: Formatter Field [1] Date: 2026-June-17 Security risk: *Critical* 19 ∕ 25 AC:None/A:User/CI:All/II:All/E:Theoretical/TD:Default [2] Vulnerability: PHP object injection Affected versions: <2.0.0 CVE IDs: CVE-2026-12535 Description: The Formatter Field module provides a mechanism for specifying a formatter and formatter settings to be used for displaying a field, on a per-entity basis. formatter_field stores some data as PHP-serialized strings. In some situations, malicious data can be written directly to the field. This can lead to an Object Injection vulnerability when the data are unserialized. This vulnerability is mitigated by the fact that an attacker must have permission to edit a content entity with an attached formatter_field field. In addition, the core JSON:API module must be enabled with the option "Accept all JSON:API create, read, update, and delete operations", which is not the default, or the attacker needs some other way to edit field values directly. Solution: Install the latest version: * If you use the Formatter Field module, upgrade to Formatter Field 2.0.0 [3]. Reported By: * Drew Webber (mcdruid) [4] of the Drupal Security Team Fixed By: * Kostia Bohach (_shy) [5] Coordinated By: * Benji Fisher (benjifisher) [6] of the Drupal Security Team * Drew Webber (mcdruid) [7] of the Drupal Security Team * Jess (xjm) [8] of the Drupal Security Team Security issue: https://git.drupalcode.org/security/185191-formatter_field-security/-/work_… [9] ------------------------------------------------------------------------------ Contribution record [10] [1] https://www.drupal.org/project/formatter_field [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/formatter_field/releases/2.0.0 [4] https://www.drupal.org/u/mcdruid [5] https://www.drupal.org/u/_shy [6] https://www.drupal.org/u/benjifisher [7] https://www.drupal.org/u/mcdruid [8] https://www.drupal.org/u/xjm [9] https://git.drupalcode.org/security/185191-formatter_field-security/-/work_… [10] https://new.drupal.org/contribution-record?source_link=https%3A//www.drupal…

1 0

Drupal core - Moderately critical - Improper validation - SA-CORE-2026-009
by security-news＠drupal.org 17 Jun '26

17 Jun '26

View online: https://www.drupal.org/sa-core-2026-009 Project: Drupal core [1] Date: 2026-June-02 Security risk: *Moderately critical* 11 ∕ 25 AC:Complex/A:User/CI:Some/II:Some/E:Theoretical/TD:Uncommon [2] Vulnerability: Improper validation Affected versions: <10.5.12 || >=10.6.0 <10.6.11 || >=11.2.0 <11.2.14 || >=11.3.0 <11.3.12 || 11.0.* || 11.1.* CVE IDs: CVE-2026-55808 Description: The JSON:API and REST modules allow you to upload image files to image fields. The validation rules check the file extension of the uploaded file but not the file MIME type. This may allow a malicious user to upload a file that is not an image. Certain web-server configurations may serve the uploaded file with its actual MIME type rather than an image type. This may lead to cross-site scripting (XSS) or other unexpected behavior. Solution: Install the latest version: *Drupal 11* * If you use Drupal 11.3.x, update to Drupal 11.3.12 [3]. * If you use Drupal 11.2.x, update to Drupal 11.2.14 [4]. *Drupal 10* * If you use Drupal 10.6.x, update to Drupal 10.6.11 [5]. * If you use Drupal 10.5.x, update to Drupal 10.5.12 [6]. Drupal 11.1.x, Drupal 11.0.x, Drupal 10.4.x, and below are end-of-life and do not receive security coverage. (Drupal 8 [7] and Drupal 9 [8] have both reached end-of-life.) Reported By: * cantina_security [9] Fixed By: * Björn Brala (bbrala) [10] * Kim Pepper (kim.pepper) [11] * Lee Rowlands (larowlan) [12] of the Drupal Security Team Coordinated By: * Damien McKenna (damienmckenna) [13] of the Drupal Security Team * Greg Knaddison (greggles) [14] of the Drupal Security Team * Lee Rowlands (larowlan) [15] of the Drupal Security Team * Dave Long (longwave) [16] of the Drupal Security Team * Juraj Nemec (poker10) [17] of the Drupal Security Team * Jess (xjm) [18] of the Drupal Security Team Security issue: https://git.drupalcode.org/security/185032-drupal-security/-/work_items/1 [19] ------------------------------------------------------------------------------ Contribution record [20] [1] https://www.drupal.org/project/drupal [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/drupal/releases/11.3.12 [4] https://www.drupal.org/project/drupal/releases/11.2.14 [5] https://www.drupal.org/project/drupal/releases/10.6.11 [6] https://www.drupal.org/project/drupal/releases/10.5.12 [7] https://www.drupal.org/psa-2021-06-29 [8] https://www.drupal.org/psa-2023-11-01 [9] https://www.drupal.org/u/cantina_security [10] https://www.drupal.org/u/bbrala [11] https://www.drupal.org/u/kimpepper [12] https://www.drupal.org/u/larowlan [13] https://www.drupal.org/u/damienmckenna [14] https://www.drupal.org/u/greggles [15] https://www.drupal.org/u/larowlan [16] https://www.drupal.org/u/longwave [17] https://www.drupal.org/u/poker10 [18] https://www.drupal.org/u/xjm [19] https://git.drupalcode.org/security/185032-drupal-security/-/work_items/1 [20] https://new.drupal.org/contribution-record?source_link=https%3A//www.drupal…

1 0

Drupal core - Moderately critical - Server-side request forgery - SA-CORE-2026-008
by security-news＠drupal.org 17 Jun '26

17 Jun '26

View online: https://www.drupal.org/sa-core-2026-008 Project: Drupal core [1] Date: 2026-June-02 Security risk: *Moderately critical* 10 ∕ 25 AC:Basic/A:User/CI:Some/II:None/E:Theoretical/TD:Default [2] Vulnerability: Server-side request forgery Affected versions: <10.5.12 || >=10.6.0 <10.6.11 || >=11.2.0 <11.2.14 || >=11.3.0 <11.3.12 || 11.0.* || 11.1.* CVE IDs: CVE-2026-55807 Description: The Media module comes with support for oEmbed. The oEmbed specification contains two discovery mechanisms, via providers.json and via URL discovery. The URL discovery code could be leveraged to trick Drupal into making server-side requests to any URL. Solution: Install the latest version: *Drupal 11* * If you use Drupal 11.3.x, update to Drupal 11.3.12 [3]. * If you use Drupal 11.2.x, update to Drupal 11.2.14 [4]. *Drupal 10* * If you use Drupal 10.6.x, update to Drupal 10.6.11 [5]. * If you use Drupal 10.5.x, update to Drupal 10.5.12 [6]. Drupal 11.1.x, Drupal 11.0.x, Drupal 10.4.x, and below are end-of-life and do not receive security coverage. (Drupal 8 [7] and Drupal 9 [8] have both reached end-of-life.) .. Required site changes for URL discovery Most users of the oEmbed functionality in Drupal likely use providers.json to define known providers (such as YouTube and Vimeo) for embedding content. If you are using URL discovery, you now need to set a list of trusted oEmbed discovery hosts in settings.php. This is an array containing a series of regular expressions for matching host names for discovery. It follows the same pattern as the existing trusted hosts settings [9]. Example: // Only allow URL discovery from example.com. $settings['media_oembed_discovery_trusted_host_patterns'] = [ '^example\.com$', ]; Reported By: * Hamed Kohi (0xhamy) [10] * assaf alassaf (ama62) [11] * Albert Skibinski (askibinski) [12] * Jon Minder (ayalon) [13] * Lautaro Casanova (betah4k) [14] * Gabe Sullice (gabesullice) [15] * John Morahan (john morahan) [16] * Michael Winser (michaelwinser) [17] * nbanderson [18] * offensive-ai [19] * Francesco Placella (plach) [20] * quynh ho (qquynh) [21] * Himanshu Anand (unknownhad) [22] Fixed By: * Lee Rowlands (larowlan) [23] of the Drupal Security Team * Dave Long (longwave) [24] of the Drupal Security Team * Drew Webber (mcdruid) [25] of the Drupal Security Team * Adam G-H (phenaproxima) [26] * Sean Blommaert (seanb) [27] Coordinated By: * Benji Fisher (benjifisher) [28] of the Drupal Security Team * cilefen (cilefen) [29] of the Drupal Security Team * Damien McKenna (damienmckenna) [30] of the Drupal Security Team * Mori Sugimoto (dokumori) [31] of the Drupal Security Team * Greg Knaddison (greggles) [32] of the Drupal Security Team * Lee Rowlands (larowlan) [33] of the Drupal Security Team * Dave Long (longwave) [34] of the Drupal Security Team * Drew Webber (mcdruid) [35] of the Drupal Security Team * James Gilliland (neclimdul) [36] of the Drupal Security Team * Juraj Nemec (poker10) [37] of the Drupal Security Team * Jess (xjm) [38] of the Drupal Security Team Security issue: https://git.drupalcode.org/security/185053-drupal-security/-/work_items/1 [39] ------------------------------------------------------------------------------ Contribution record [40] [1] https://www.drupal.org/project/drupal [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/drupal/releases/11.3.12 [4] https://www.drupal.org/project/drupal/releases/11.2.14 [5] https://www.drupal.org/project/drupal/releases/10.6.11 [6] https://www.drupal.org/project/drupal/releases/10.5.12 [7] https://www.drupal.org/psa-2021-06-29 [8] https://www.drupal.org/psa-2023-11-01 [9] https://www.drupal.org/docs/getting-started/installing-drupal/trusted-host-… [10] https://www.drupal.org/u/0xhamy [11] https://www.drupal.org/u/ama62 [12] https://www.drupal.org/u/askibinski [13] https://www.drupal.org/u/ayalon [14] https://www.drupal.org/u/betah4k [15] https://www.drupal.org/u/gabesullice [16] https://www.drupal.org/u/john-morahan [17] https://www.drupal.org/u/michaelwinser [18] https://www.drupal.org/u/nbanderson [19] https://www.drupal.org/u/offensive-ai [20] https://www.drupal.org/u/plach [21] https://www.drupal.org/u/qquynh [22] https://www.drupal.org/u/unknownhad [23] https://www.drupal.org/u/larowlan [24] https://www.drupal.org/u/longwave [25] https://www.drupal.org/u/mcdruid [26] https://www.drupal.org/u/phenaproxima [27] https://www.drupal.org/u/seanb [28] https://www.drupal.org/u/benjifisher [29] https://www.drupal.org/u/cilefen [30] https://www.drupal.org/u/damienmckenna [31] https://www.drupal.org/u/dokumori [32] https://www.drupal.org/u/greggles [33] https://www.drupal.org/u/larowlan [34] https://www.drupal.org/u/longwave [35] https://www.drupal.org/u/mcdruid [36] https://www.drupal.org/u/neclimdul [37] https://www.drupal.org/u/poker10 [38] https://www.drupal.org/u/xjm [39] https://git.drupalcode.org/security/185053-drupal-security/-/work_items/1 [40] https://new.drupal.org/contribution-record?source_link=https%3A//www.drupal…

1 0

Drupal core - Moderately critical - Gadget chain - SA-CORE-2026-006
by security-news＠drupal.org 17 Jun '26

17 Jun '26

View online: https://www.drupal.org/sa-core-2026-006 Project: Drupal core [1] Date: 2026-June-08 Security risk: *Moderately critical* 14 ∕ 25 AC:Complex/A:Admin/CI:All/II:All/E:Theoretical/TD:Uncommon [2] Vulnerability: Gadget chain Affected versions: <10.5.12 || >=10.6.0 <10.6.11 || >=11.2.0 <11.2.14 || >=11.3.0 <11.3.12 || >=11.4.0 <11.4.0-rc2 || 11.0.* || 11.1.* CVE IDs: CVE-2026-55804 Description: Drupal core contains a chain of methods that could be exploitable when an insecure deserialization vulnerability exists on the site. This so-called "gadget chain" presents no direct threat, but is a vector that can be used to achieve remote code execution or SQL injection if the application deserializes untrusted data due to another vulnerability. This issue is not directly exploitable. This issue is mitigated by the fact that in order for it to be exploitable, a separate vulnerability must be present to allow an attacker to pass unsafe input to unserialize(). Solution: Install the latest version: *Drupal 11* * If you use Drupal 11.3.x, update to Drupal 11.3.12 [3]. * If you use Drupal 11.2.x, update to Drupal 11.2.14 [4]. *Drupal 10* * If you use Drupal 10.6.x, update to Drupal 10.6.11 [5]. * If you use Drupal 10.5.x, update to Drupal 10.5.12 [6]. Drupal 11.1.x, Drupal 11.0.x, Drupal 10.4.x, and below are end-of-life and do not receive security coverage. (Drupal 8 [7] and Drupal 9 [8] have both reached end-of-life.) Reported By: * Michael Maturi (michaelmaturi) [9] Fixed By: * Lee Rowlands (larowlan) [10] of the Drupal Security Team * Drew Webber (mcdruid) [11] of the Drupal Security Team * Mohit Aghera (mohit_aghera) [12] Coordinated By: * Anna Kalata (akalata) [13] of the Drupal Security Team * Benji Fisher (benjifisher) [14] of the Drupal Security Team * cilefen (cilefen) [15] of the Drupal Security Team * Greg Knaddison (greggles) [16] of the Drupal Security Team * Lee Rowlands (larowlan) [17] of the Drupal Security Team * Dave Long (longwave) [18] of the Drupal Security Team * Drew Webber (mcdruid) [19] of the Drupal Security Team * Juraj Nemec (poker10) [20] of the Drupal Security Team * Jess (xjm) [21] of the Drupal Security Team Security issue: https://git.drupalcode.org/security/185171-drupal-security/-/work_items/1 [22] ------------------------------------------------------------------------------ Contribution record [23] [1] https://www.drupal.org/project/drupal [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/drupal/releases/11.3.12 [4] https://www.drupal.org/project/drupal/releases/11.2.14 [5] https://www.drupal.org/project/drupal/releases/10.6.11 [6] https://www.drupal.org/project/drupal/releases/10.5.12 [7] https://www.drupal.org/psa-2021-06-29 [8] https://www.drupal.org/psa-2023-11-01 [9] https://www.drupal.org/u/michaelmaturi [10] https://www.drupal.org/u/larowlan [11] https://www.drupal.org/u/mcdruid [12] https://www.drupal.org/u/mohit_aghera [13] https://www.drupal.org/u/akalata [14] https://www.drupal.org/u/benjifisher [15] https://www.drupal.org/u/cilefen [16] https://www.drupal.org/u/greggles [17] https://www.drupal.org/u/larowlan [18] https://www.drupal.org/u/longwave [19] https://www.drupal.org/u/mcdruid [20] https://www.drupal.org/u/poker10 [21] https://www.drupal.org/u/xjm [22] https://git.drupalcode.org/security/185171-drupal-security/-/work_items/1 [23] https://new.drupal.org/contribution-record?source_link=https%3A//www.drupal…

1 0

Drupal core - Critical - PHP object injection - SA-CORE-2026-005
by security-news＠drupal.org 17 Jun '26

17 Jun '26

View online: https://www.drupal.org/sa-core-2026-005 Project: Drupal core [1] Date: 2026-June-05 Security risk: *Critical* 18 ∕ 25 AC:None/A:User/CI:All/II:All/E:Theoretical/TD:Uncommon [2] Vulnerability: PHP object injection Affected versions: <10.5.12 || >=10.6.0 <10.6.11 || >=11.2.0 <11.2.14 || >=11.3.0 <11.3.12 || >=11.4.0 <11.4.0-rc2 || 11.0.* || 11.1.* CVE IDs: CVE-2026-55803 Description: SA-CORE-2019-003 [3] added protection for fields that store serialized data to disallow direct writes via web services. The above fix did not cover all potential attack vectors for JSON:API. An attacker with appropriate JSON:API write permission could potentially inject a malicious payload in certain rare circumstances, potentially resulting in PHP Object Injection. This vulnerability is mitigated by the fact that in order to be exploitable: * A site must use an entity reference field type that stores a serialized property. * An attacker must have permission to write to the entity via JSON:API. No field type shipped with Drupal core meets these criteria, and contributed or user-created field types that do appear to be extremely unusual. This update protects all such fields; no changes are required in contributed modules. JSON:API is read-only by default, so sites are only affected if they have enabled write access (either through administrator configuration or the installation of a contributed or custom module that enables write access). .. DrupalSteward protection: This issue is being protected by Drupal Steward [4]. In this instance, we believe that the WAF rule will provide mitigation for the common/obvious vulnerability paths, but may not be able to cover all cases or work for all hosting providers. Additionally, several other core security advisories released today are /not/ mitigated by Drupal Steward. Therefore, our recommended action is still to plan an actual Drupal update within 24 hours of this release. Solution: Install the latest version: *Drupal 11* * If you use Drupal 11.3.x, update to Drupal 11.3.12 [5]. * If you use Drupal 11.2.x, update to Drupal 11.2.14 [6]. *Drupal 10* * If you use Drupal 10.6.x, update to Drupal 10.6.11 [7]. * If you use Drupal 10.5.x, update to Drupal 10.5.12 [8]. Drupal 11.1.x, Drupal 11.0.x, Drupal 10.4.x, and below are end-of-life and do not receive security coverage. (Drupal 8 [9] and Drupal 9 [10] have both reached end-of-life.) Reported By: * Michael Maturi (michaelmaturi) [11] Fixed By: * Björn Brala (bbrala) [12] * Sascha Grossenbacher (berdir) [13] * Lee Rowlands (larowlan) [14] of the Drupal Security Team * Dave Long (longwave) [15] of the Drupal Security Team * Drew Webber (mcdruid) [16] of the Drupal Security Team Coordinated By: * Anna Kalata (akalata) [17] of the Drupal Security Team * Benji Fisher (benjifisher) [18] of the Drupal Security Team * Damien McKenna (damienmckenna) [19] of the Drupal Security Team * David Strauss (david strauss) [20] of the Drupal Security Team * Neil Drumm (drumm) [21] of the Drupal Security Team * Greg Knaddison (greggles) [22] of the Drupal Security Team * Tim Hestenes Lehnen (hestenet) [23] * Lee Rowlands (larowlan) [24] of the Drupal Security Team * Dave Long (longwave) [25] of the Drupal Security Team * Drew Webber (mcdruid) [26] of the Drupal Security Team * Juraj Nemec (poker10) [27] of the Drupal Security Team * Ra Mänd (ram4nd) [28] provisional member of the Drupal Security Team * Jess (xjm) [29] of the Drupal Security Team Security issue: https://git.drupalcode.org/security/185158-drupal-security/-/work_items/1 [30] ------------------------------------------------------------------------------ Contribution record [31] [1] https://www.drupal.org/project/drupal [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/sa-core-2019-003 [4] https://www.drupal.org/steward [5] https://www.drupal.org/project/drupal/releases/11.3.12 [6] https://www.drupal.org/project/drupal/releases/11.2.14 [7] https://www.drupal.org/project/drupal/releases/10.6.11 [8] https://www.drupal.org/project/drupal/releases/10.5.12 [9] https://www.drupal.org/psa-2021-06-29 [10] https://www.drupal.org/psa-2023-11-01 [11] https://www.drupal.org/u/michaelmaturi [12] https://www.drupal.org/u/bbrala [13] https://www.drupal.org/u/berdir [14] https://www.drupal.org/u/larowlan [15] https://www.drupal.org/u/longwave [16] https://www.drupal.org/u/mcdruid [17] https://www.drupal.org/u/akalata [18] https://www.drupal.org/u/benjifisher [19] https://www.drupal.org/u/damienmckenna [20] https://www.drupal.org/u/david-strauss [21] https://www.drupal.org/u/drumm [22] https://www.drupal.org/u/greggles [23] https://www.drupal.org/u/hestenet [24] https://www.drupal.org/u/larowlan [25] https://www.drupal.org/u/longwave [26] https://www.drupal.org/u/mcdruid [27] https://www.drupal.org/u/poker10 [28] https://www.drupal.org/u/ram4nd [29] https://www.drupal.org/u/xjm [30] https://git.drupalcode.org/security/185158-drupal-security/-/work_items/1 [31] https://new.drupal.org/contribution-record?source_link=https%3A//www.drupal…

1 0

Brute force attack protection - Critical - Unsupported - SA-CONTRIB-2026-047
by security-news＠drupal.org 10 Jun '26

10 Jun '26

View online: https://www.drupal.org/sa-contrib-2026-047 Project: Brute force attack protection [1] Date: 2026-June-10 Security risk: *Critical* 16 ∕ 25 AC:Complex/A:Admin/CI:All/II:All/E:Theoretical/TD:All [2] Vulnerability: Unsupported Affected versions: * CVE IDs: CVE-2026-11915 Description: The security team is marking this project unsupported. There is a known security issue with the project that has not been fixed by the maintainer. If you would like to maintain this project, please read: https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mai... [3] Solution: If you use this project, you should uninstall it. To take over maintainership, please read https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mai... [4] ------------------------------------------------------------------------------ Contribution record [5] [1] https://www.drupal.org/project/bfap_sb [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mainta… [4] https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mainta… [5] https://new.drupal.org/contribution-record?source_link=https%3A//www.drupal…

1 0

Composer - Critical - Unsupported - SA-CONTRIB-2026-046
by security-news＠drupal.org 10 Jun '26

10 Jun '26

View online: https://www.drupal.org/sa-contrib-2026-046 Project: Composer [1] Date: 2026-June-10 Security risk: *Critical* 16 ∕ 25 AC:Complex/A:Admin/CI:All/II:All/E:Theoretical/TD:All [2] Vulnerability: Unsupported Affected versions: * CVE IDs: CVE-2026-11914 Description: The security team is marking the Composer module for Drupal project unsupported. There is a known security issue with the project that has not been fixed by the maintainer. If you would like to maintain this project, please read: https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mai... [3] /Note: this is about a project for the Drupal system that makes use of composer. It is not a vulnerability in the composer software itself./ Solution: If you use this project, you should uninstall it. To take over maintainership, please read https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mai... [4] ------------------------------------------------------------------------------ Contribution record [5] [1] https://www.drupal.org/project/composer [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mainta… [4] https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mainta… [5] https://new.drupal.org/contribution-record?source_link=https%3A//www.drupal…

1 0

Mother May I - Critical - Unsupported - SA-CONTRIB-2026-045
by security-news＠drupal.org 10 Jun '26

10 Jun '26

View online: https://www.drupal.org/sa-contrib-2026-045 Project: Mother May I [1] Date: 2026-June-10 Security risk: *Critical* 16 ∕ 25 AC:Complex/A:Admin/CI:All/II:All/E:Theoretical/TD:All [2] Vulnerability: Unsupported Affected versions: * CVE IDs: CVE-2026-11913 Description: The security team is marking this project unsupported. There is a known security issue with the project that has not been fixed by the maintainer. If you would like to maintain this project, please read: https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mai... [3] Solution: If you use this project, you should uninstall it. To take over maintainership, please read https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mai... [4] ------------------------------------------------------------------------------ Contribution record [5] [1] https://www.drupal.org/project/mothermayi [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mainta… [4] https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mainta… [5] https://new.drupal.org/contribution-record?source_link=https%3A//www.drupal…

1 0

Examples for Developers - Moderately critical - Access bypass - SA-CONTRIB-2026-044
by security-news＠drupal.org 10 Jun '26

10 Jun '26

View online: https://www.drupal.org/sa-contrib-2026-044 Project: Examples for Developers [1] Date: 2026-June-10 Security risk: *Moderately critical* 11 ∕ 25 AC:Basic/A:Admin/CI:Some/II:Some/E:Theoretical/TD:Uncommon [2] Vulnerability: Access bypass Affected versions: <4.0.6 CVE IDs: CVE-2026-11909 Description: The Examples for Developers project aims to provide high-quality, well-documented API examples for a broad range of Drupal core functionality. The "Read from a file" feature implemented by the file_example submodule can be used to expose any file that PHP can access. Therefore, the file_example sub-module is being removed from Examples for Developers until a version demonstrating file security best practices can be added back in the future. Developers who based a new module on this example should review their code for an access bypass. Solution: Any site with the file_example submodule installed should uninstall it immediately. Then, install the latest version of Examples for Developers: * If you are using Examples for Developers 4.0.x, upgrade to Examples for Developers 4.0.6 [3]. Developers who based a new module on this example should review their code for an access bypass. Reported By: * Pierre Rudloff (prudloff) [4] of the Drupal Security Team Fixed By: * Alberto Paderno (avpaderno) [5] * Pierre Rudloff (prudloff) [6] of the Drupal Security Team Coordinated By: * Greg Knaddison (greggles) [7] of the Drupal Security Team * Juraj Nemec (poker10) [8] of the Drupal Security Team Security issue: https://git.drupalcode.org/security/42-examples-security/-/work_items/1 [9] ------------------------------------------------------------------------------ Contribution record [10] [1] https://www.drupal.org/project/examples [2] https://www.drupal.org/security-team/risk-levels [3] https://www.drupal.org/project/examples/releases/4.0.6 [4] https://www.drupal.org/u/prudloff [5] https://www.drupal.org/u/avpaderno [6] https://www.drupal.org/u/prudloff [7] https://www.drupal.org/u/greggles [8] https://www.drupal.org/u/poker10 [9] https://git.drupalcode.org/security/42-examples-security/-/work_items/1 [10] https://new.drupal.org/contribution-record?source_link=https%3A//www.drupal…

1 0