You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No further updates to Strapi 4 will be published, this release serves as the final version of Strapi 4 which is considered EOL (End-Of-Life) as of April 30th, 2026. All Strapi users should migrate to Strapi 5: https://docs.strapi.io/cms/migration/v4-to-v5/introduction-and-faq
Also please note, this does include Strapi Customers as well. Strapi Cloud will still continue to function with Strapi 4 but that may be subject change in the near future without warning.
What's Changed
Security
Fixed a critical vulnerability where relational filtering could expose sensitive data through insufficient query sanitization. See GHSA-rjg2-95x7-8qmx / CVE-2026-27886.
Upgraded tar to v7 to address security warnings.
Applied v4 dependency security and maintenance updates.
Fixes
Enforced unique admin email validation when updating the authenticated user profile.
Strapi was made aware of a vulnerably that were patched in this release, for now we are going to delay the detailed disclosure of the exact details on how to exploit it and how it was patched to give time for users to upgrade before we do public disclosure.
What's Changed
fix(content-type-builder): make write APIs accessible in devMode only by @nclsndr in #25133
Strapi was made aware of a vulnerably that were patched in this release, for now we are going to delay the detailed disclosure of the exact details on how to exploit it and how it was patched to give time for users to upgrade before we do public disclosure.
Strapi was made aware of a vulnerably that were patched in this release, for now we are going to delay the detailed disclosure of the exact details on how to exploit it and how it was patched to give time for users to upgrade before we do public disclosure.
Strapi was made aware of a vulnerably that were patched in this release, for now we are going to delay the detailed disclosure of the exact details on how to exploit it and how it was patched to give time for users to upgrade before we do public disclosure.
🔥 Bug fix
[core:content-manager] fix: Creating a new locale doesn't pre-fill the non-internationalized fields (#18773) @derrickmehaffy
[core:content-manager] fix: show name of relations when lazy loading them (#19915) @Marc-Roig
[core:content-releases] fix(releases): Scheduling info capitalization (#19945) @madhurisandbhor
[core:content-releases] fix(releases): On edit release error dont close modal (#19946) @madhurisandbhor
[core:upload] fix: sanitize file name when uploading image (#19913) @Marc-Roig
[plugin:i18n] fix:issue on do not validate locale if not creating for all locales (#19799) @binar1
[core:content-manager] fix(content-manager): fix strange behaviours when you change position on Dynamic Zones and solve issue with ids not unique (#19480) @simotae14
Next steps: Take a moment to review the security alert above. Review
the linked package source code to understand the potential risk. Ensure the
package is not malicious before proceeding. If you're unsure how to proceed,
reach out to your security team or ask the Socket team for help at
support@socket.dev.
Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/@esbuild/aix-ppc64@0.19.12. You can
also ignore all packages with @SocketSecurity ignore-all.
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
Warn
Obfuscated code: npm @internationalized/date is 90.0% likely obfuscated
Next steps: Take a moment to review the security alert above. Review
the linked package source code to understand the potential risk. Ensure the
package is not malicious before proceeding. If you're unsure how to proceed,
reach out to your security team or ask the Socket team for help at
support@socket.dev.
Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/@internationalized/date@3.12.2. You can
also ignore all packages with @SocketSecurity ignore-all.
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
Warn
Obfuscated code: npm @pnpm/network.ca-file is 90.0% likely obfuscated
Next steps: Take a moment to review the security alert above. Review
the linked package source code to understand the potential risk. Ensure the
package is not malicious before proceeding. If you're unsure how to proceed,
reach out to your security team or ask the Socket team for help at
support@socket.dev.
Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/@pnpm/network.ca-file@1.0.2. You can
also ignore all packages with @SocketSecurity ignore-all.
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
Warn
Obfuscated code: npm commander is 90.0% likely obfuscated
Next steps: Take a moment to review the security alert above. Review
the linked package source code to understand the potential risk. Ensure the
package is not malicious before proceeding. If you're unsure how to proceed,
reach out to your security team or ask the Socket team for help at
support@socket.dev.
Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/commander@10.0.1. You can
also ignore all packages with @SocketSecurity ignore-all.
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
Warn
Obfuscated code: npm entities is 91.0% likely obfuscated
Next steps: Take a moment to review the security alert above. Review
the linked package source code to understand the potential risk. Ensure the
package is not malicious before proceeding. If you're unsure how to proceed,
reach out to your security team or ask the Socket team for help at
support@socket.dev.
Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/entities@4.5.0. You can
also ignore all packages with @SocketSecurity ignore-all.
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
Warn
Obfuscated code: npm js-yaml is 90.0% likely obfuscated
Next steps: Take a moment to review the security alert above. Review
the linked package source code to understand the potential risk. Ensure the
package is not malicious before proceeding. If you're unsure how to proceed,
reach out to your security team or ask the Socket team for help at
support@socket.dev.
Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/js-yaml@4.2.0. You can
also ignore all packages with @SocketSecurity ignore-all.
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
Warn
Obfuscated code: npm rimraf is 90.0% likely obfuscated
Next steps: Take a moment to review the security alert above. Review
the linked package source code to understand the potential risk. Ensure the
package is not malicious before proceeding. If you're unsure how to proceed,
reach out to your security team or ask the Socket team for help at
support@socket.dev.
Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/rimraf@5.0.10. You can
also ignore all packages with @SocketSecurity ignore-all.
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
Warn
Obfuscated code: npm stream-json is 90.0% likely obfuscated
Next steps: Take a moment to review the security alert above. Review
the linked package source code to understand the potential risk. Ensure the
package is not malicious before proceeding. If you're unsure how to proceed,
reach out to your security team or ask the Socket team for help at
support@socket.dev.
Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/stream-json@1.8.0. You can
also ignore all packages with @SocketSecurity ignore-all.
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
Warn
Obfuscated code: npm webpack is 90.0% likely obfuscated
Next steps: Take a moment to review the security alert above. Review
the linked package source code to understand the potential risk. Ensure the
package is not malicious before proceeding. If you're unsure how to proceed,
reach out to your security team or ask the Socket team for help at
support@socket.dev.
Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/webpack@5.107.2. You can
also ignore all packages with @SocketSecurity ignore-all.
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
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
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.
This PR contains the following updates:
4.1.6→4.26.24.1.5→4.25.234.1.5→4.26.24.1.5→4.26.2Release Notes
strapi/strapi (@strapi/plugin-graphql)
v4.26.2Compare Source
No further updates to Strapi 4 will be published, this release serves as the final version of Strapi 4 which is considered EOL (End-Of-Life) as of April 30th, 2026. All Strapi users should migrate to Strapi 5: https://docs.strapi.io/cms/migration/v4-to-v5/introduction-and-faq
Also please note, this does include Strapi Customers as well. Strapi Cloud will still continue to function with Strapi 4 but that may be subject change in the near future without warning.
What's Changed
Security
tarto v7 to address security warnings.Fixes
Compatibility
Full Changelog: strapi/strapi@v4.26.1...v4.26.2
v4.26.1Compare Source
Strapi was made aware of a vulnerably that were patched in this release, for now we are going to delay the detailed disclosure of the exact details on how to exploit it and how it was patched to give time for users to upgrade before we do public disclosure.
What's Changed
Full Changelog: strapi/strapi@v4.26.0...v4.26.1
v4.26.0Compare Source
What's Changed
Full Changelog: strapi/strapi@v4.25.24...v4.26.0
v4.25.24Compare Source
What's Changed
New Contributors
Full Changelog: strapi/strapi@v4.25.23...v4.25.24
v4.25.23Compare Source
What's Changed
v4.25.22Compare Source
🚨 Security
📚 Update and Migration Guides
v4.25.21Compare Source
What's Changed
Full Changelog: strapi/strapi@v4.25.20...v4.25.21
v4.25.20Compare Source
What's Changed
Full Changelog: strapi/strapi@v4.25.19...v4.25.20
v4.25.19Compare Source
What's Changed
Full Changelog: strapi/strapi@v4.25.17...v4.25.19
v4.25.18Compare Source
v4.25.17Compare Source
🔥 Bug fix
📚 Update and Migration Guides
v4.25.16Compare Source
💅 Enhancement
📚 Update and Migration Guides
v4.25.15Compare Source
What's Changed
New Contributors
Full Changelog: strapi/strapi@v4.25.14...v4.25.15
v4.25.14Compare Source
What's Changed
New Contributors
Full Changelog: strapi/strapi@v4.25.13...v4.25.14
v4.25.13Compare Source
What's Changed
Full Changelog: strapi/strapi@v4.25.12...v4.25.13
v4.25.12Compare Source
💅 Enhancement
🚨 Security
🔥 Bug fix
📚 Update and Migration Guides
v4.25.11Compare Source
🔥 Bug fix
💅 Enhancement
⚙️ Chore
📚 Update and Migration Guides
v4.25.10Compare Source
🔥 Bug fix
📚 Update and Migration Guides
v4.25.9Compare Source
🔥 Bug fix
💅 Enhancement
🚨 Security
⚙️ Chore
📚 Update and Migration Guides
v4.25.8Compare Source
🚀 New feature
🔥 Bug fix
📚 Update and Migration Guides
v4.25.7Compare Source
⚙️ Chore
🔥 Bug fix
📚 Update and Migration Guides
v4.25.6Compare Source
🔥 Bug fix
📚 Update and Migration Guides
v4.25.5Compare Source
🔥 Bug fix
🚀 New feature
⚙️ Chore
📚 Update and Migration Guides
v4.25.4Compare Source
🚀 New feature
🔥 Bug fix
📚 Update and Migration Guides
v4.25.3Compare Source
🚨 Security
⚙️ Chore
📚 Update and Migration Guides
v4.25.2Compare Source
Strapi was made aware of a vulnerably that were patched in this release, for now we are going to delay the detailed disclosure of the exact details on how to exploit it and how it was patched to give time for users to upgrade before we do public disclosure.
🔥 Bug fix
💅 Enhancement
⚙️ Chore
📚 Update and Migration Guides
v4.25.1Compare Source
💅 Enhancement
📚 Update and Migration Guides
v4.25.0Compare Source
🚀 New feature
🔥 Bug fix
💅 Enhancement
🚨 Security
📚 Update and Migration Guides
v4.24.5Compare Source
What's Changed
New Contributors
Full Changelog: strapi/strapi@v4.24.4...v4.24.5
v4.24.4Compare Source
🔥 Bug fix
📚 Update and Migration Guides
v4.24.3Compare Source
🔥 Bug fix
📚 Update and Migration Guides
v4.24.2Compare Source
Strapi was made aware of a vulnerably that were patched in this release, for now we are going to delay the detailed disclosure of the exact details on how to exploit it and how it was patched to give time for users to upgrade before we do public disclosure.
📚 Update and Migration Guides
Full Changelog: strapi/strapi@v4.24.2...v4.24.1
v4.24.1Compare Source
🔥 Bug fix
📚 Update and Migration Guides
v4.24.0Compare Source
🔥 Bug fix
⚙️ Chore
📚 Update and Migration Guides
v4.23.2Compare Source
What's Changed
Full Changelog: strapi/strapi@v4.23.1...v4.23.2
v4.23.1Compare Source
📖 Documentation
⚙️ Chore
🔥 Bug fix
📚 Update and Migration Guides
v4.23.0Compare Source
⚙️ Chore
[external] Update sharp package to version v0.33.3 (#19311) @mariansimecek🔥 Bug fix
🚀 New feature
💅 Enhancement
📚 Update and Migration Guides
v4.22.1Compare Source
What's Changed
Full Changelog: strapi/strapi@v4.22.0...v4.22.1
v4.22.0Compare Source
Strapi was made aware of a vulnerably that were patched in this release, for now we are going to delay the detailed disclosure of the exact details on how to exploit it and how it was patched to give time for users to upgrade before we do public disclosure.
🔥 Bug fix
🚀 New feature
⚙️ Chore
📚 Update and Migration Guides
v4.21.1Compare Source
💅 Enhancement
🔥 Bug fix
📚 Update and Migration Guides
v4.21.0Compare Source
💅 Enhancement
🚀 New feature
📚 Update and Migration Guides
v4.20.5Compare Source
🔥 Bug fix
⚙️ Chore
📚 Update and Migration Guides
v4.20.4Compare Source
💅 Enhancement
🔥 Bug fix
⚙️ Chore
📚 Update and Migration Guides
v4.20.3Compare Source
🔥 Bug fix
📚 Update and Migration Guides
v4.20.2Compare Source
🔥 Bug fix
📚 Update and Migration Guides
v4.20.1Compare Source
💅 Enhancement
🔥 Bug fix
⚙️ Chore
📖 Documentation
🚀 New feature
📚 Update and Migration Guides
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.