CVE-2026-103035: TeamPass folder re-parenting authorization bypass

Published Nov 19, 2026
·
Updated

TeamPass is a self-hosted collaborative password manager. Prior to 3.2.1.2, the updatefolder action in app/sources/folders.queries.php allowed an authenticated, non-read-only user to re-parent a folder without checking whether the target folder or submitted parentId belonged to the caller's user-accessiblefolders set. Selecting a personal folder as the new parent passed the personal-folder guard and set personalfolder on the target, transferring the credential subtree into the attacker's accessible space after the next login and hiding it from the organization, including administrators. The change exposed credential labels, logins, URLs, email addresses, and descriptions, while sharekey-protected passwords remained protected; hiding the subtree also denied other users access. This issue is fixed in version 3.2.1.2.

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.2.1.2

Event History

Nov 19, 2026
CVE Published
via MITRE·06:22 PM
Data Sourced
via MITRE·06:22 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

An authenticated TeamPass user whose account is not read-only can exploit it. The attacker needs access to the update_folder action but does not need another user's credentials or interaction.

2

What data and impact are exposed if exploitation succeeds?

The attacker can move a credential subtree into their accessible personal-folder space. This exposes credential labels, logins, URLs, email addresses, and descriptions, while passwords protected by sharekeys remain protected; the move also hides the subtree from the organization, including administrators, and denies other users access.

3

Are default deployments affected?

The issue affects TeamPass versions before 3.2.1.2 when authenticated users have non-read-only access. Exploitation relies on the missing authorization checks for the target folder and submitted parentId.

4

What should teams do if they cannot patch immediately?

Restrict non-read-only access to trusted users where possible, because those accounts can perform the unauthorized folder re-parenting. Monitor for folders unexpectedly moved into personal-folder space or becoming inaccessible to their expected organizational users.

5

How can administrators tell whether they may have been affected?

Look for credential subtrees that are unexpectedly hidden from the organization or administrators and unavailable to users who previously had access. Affected content may instead be associated with a user's personal-folder space after that user logs in.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203