Members whose last team was deleted kept access to suborganizations through the All Organization Members team

PPSA-202611-1


Summary

When a team was deleted, a member for whom it was the last team left the organization, but stayed a member of the All Organization Members team in the suborganizations that team had been added to. Until any later change of team members in the organization, the member kept the access this team gave them in these suborganizations.

Who was affected

Organizations on Private Packagist Cloud until the fix on November 13, 2026, and on Private Packagist Self-Hosted installations running a version before 2.0.40, if all of the following are true:

  • The organization uses suborganizations, and its All Organization Members team had been added to at least one of them.
  • An owner or admin deleted a team, on the Teams page or through the API.
  • For a member of the deleted team, it was their last team, apart from the Billing team.

Only such a member kept access, and only in the suborganizations the All Organization Members team had been added to. The access lasted until any later change of team members in the organization, for example adding or removing a member of any team, which updated the teams of the suborganizations.

Removing a member from a team or from the organization was not affected and removed the member from the suborganization teams right away.

Impact

A member who left the organization when their last team was deleted could have kept downloading the packages the All Organization Members team had access to in the suborganizations it had been added to, with their own Composer credentials, and could have kept using these suborganizations in the web interface with the team's permissions. If the team had admin access to a suborganization, this included managing that suborganization. The member was still listed in the suborganization's All Organization Members team.

The member lost access to the main organization right away. The member kept no access beyond what the All Organization Members team had in the suborganizations, and could not access suborganizations the team had not been added to.

What we did

Deleting a team now also removes the members who leave the organization from the All Organization Members team of every suborganization right away, and they lose its access there right away. The fix was deployed on Private Packagist Cloud on November 13, 2026, and released in Private Packagist Self-Hosted 2.0.40. We found this vulnerability during internal work on member management.

On November 13, 2026, we checked the All Organization Members team of every suborganization on Private Packagist Cloud. None of them had a member who was no longer a member of the main organization's All Organization Members team.

Do customers need to do anything

  • Private Packagist Self-Hosted: Upgrade to 2.0.40 or any later version. We recommend upgrading to the latest release. The upgrade does not remove members who already stayed in a suborganization this way. If your organization added All Organization Members to suborganizations, open the All Organization Members team on the Teams page of each of these suborganizations. If it lists a user who is no longer a member of the organization, add any member to any team of the main organization and remove them again. This updates the teams of all suborganizations and removes the user.
  • Private Packagist Cloud: No action is required.

All security advisories

Start Free Trial

Login to create an organization and start your free trial!