Security: bump SPIP core to 4.4.23 - #6
Merged
Merged
Conversation
4.4.23 fixes a privilege-escalation -> RCE vulnerability (CERTFR-2026-AVI-1109, SPIP security bulletin 2026-09-02) NOT covered by the SPIP security screen, and a 4.4.22 regression that could break the public site. Bump the pinned version; the Dockerfile fetches core at build time so this is the whole change.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Bumps the pinned SPIP core from 4.4.22 to 4.4.23.
Why: 4.4.23 is a critical security release — fixes a privilege-escalation leading to RCE (CERTFR-2026-AVI-1109, SPIP bulletin 2026-09-02), not mitigated by the SPIP security screen. It also fixes a 4.4.22 regression that could break the public site.
Change: one line in
spip/SPIP_VERSION— the Dockerfile fetches SPIP core at build time, so the bump + rebuild is the whole upgrade (no DB migration step; SPIP replays its own schema upgrade on the first authenticated /ecrire visit if needed). See docs/{fr,en}/spip-upgrade.md.