-
-
Notifications
You must be signed in to change notification settings - Fork 0
Updated Drupal core to 11.4.7 and contrib modules, closing two security advisories. #331
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SA-CORE-2026-013: https://www.drupal.org/sa-core-2026-na0isdadth
SA-CONTRIB-2026-138 / CVE-2026-87940: https://www.drupal.org/sa-contrib-2026-xa9cdychdu
Two of the constraint bumps in this file are security fixes, and both advisories were live against this site rather than theoretical.
drupal/core-recommendedanddrupal/core-composer-scaffoldmove~11.4.6to~11.4.7, the release that patches a moderately-critical XSS in the bundled CKEditor 5 engine. The advisory's wording is what makes it matter here: "an attacker that can create or edit content (even without access to CKEditor themselves)" can target anyone who later opens that content in the editor, including administrators. This site is in scope -ckeditor5is enabled inconfig/default/core.extension.ymland four formats configure an editor (basic_html,civictheme_rich_text,full_html,webform_default).drupal/key_authmoves^2.2.3to^2.2.4, patching an access bypass where the module omitted per-user caching and one account could read another account's authentication keys. The advisory notes exploitation requiresdynamic_page_cache, which it treats as a non-default mitigation - but on this site that module is enabled alongsidekey_auth, so the precondition is met.key_authis what authenticates thedo_content_apiendpoints described indocs/content-api.md, so the keys at risk are the ones used to post content.The remaining constraints moved because
config.bump-after-updateistrue, so Composer rewrites the floor to whatever the lock resolved - that is why this file changed at all rather than onlycomposer.lock. Worth a reviewer's attention among them:mglaman/phpstan-drupal^2.1.2to^2.2.0made five previously always-on legacy rules configurable and corrected a wrong error identifier, either of which can shift what static analysis reports. Verified locally:ahoy lintis green, with PHPStan and Rector both reporting no errors, so no baseline or config change was needed.behat/behat^3.32.0to^3.33.0adds Cucumber tag expressions - the reasoncucumber/tag-expressionsappears as a new lock entry with no matching line here, since it is a transitive dependency. It also adds a deprecation when a step definition's parameter count disagrees with its function signature, and fixes scenarios that failed only inside a hook never being re-run, so a previously-hidden failure can surface in CI.drupal/entity_usage^2.2@betato^2.3@betais the only minor contrib bump.drush updatedb:statusreports no database updates required, so it ships nothing this site has to run on deploy.No
extra.patchesentry needed re-rolling - all six patches still apply, andpatches.lock.jsonis unchanged. There is noconfig.audit.ignoreblock in this file, so nothing was pruned there.composer audit --lockedreports these two advisories against thedeveloplock and none against this branch.