fix: apply upstream security patch to remove activation_key exposure from account API#1366
Merged
ahmed-arb merged 2 commits intooverhangio:releasefrom Apr 17, 2026
Conversation
fd4b8d9 to
fd339b1
Compare
Contributor
Author
|
@regisb could you please take a look at this security backport? |
Collaborator
|
Thank you @Gi-ron, could you please verify if you have tested image builds with this patch? |
Contributor
Author
|
@ahmed-arb Yes I have tested the image builds with this patch and everything is working correctly. No issues found. |
Collaborator
|
Okay, merging it then. |
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
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.
Description
This PR applies an upstream security fix from Open edX by backporting the following commit into the Tutor Open edX Docker image, which removes the activation_key field from the /api/user/v1/accounts/{username} response to prevent a vulnerability where attackers could bypass email verification by combining OAuth2 password grant access for inactive users with direct account activation:
openedx/openedx-platform@21cead2
This issue is part of the security advisory discussed here:
https://discuss.openedx.org/t/security-upcoming-security-release-for-openedx-platform-2026-03-27/18655
This PR is proposed because the fix is not yet included in an official Open edX Ulmo release used by Tutor. Applying it at build time ensures that Tutor deployments are protected until the fix is available upstream in a stable release.