Skip to main content
Menu
CVEs

TeamPass authorization bypass in folder re-parenting

Affects TeamPass up to 3.2.1.1 for authenticated users who are not read-only. Fixed in 3.2.1.2.

CVE-2026-103035Published November 19, 2026, updated

8.3HighCNA
Exploited
No known exploitation
Fix
Fixed in 3.2.1.2
Who is exposed
Specific setups only

Summary

TeamPass, a self-hosted collaborative password manager from nilsteampassnet, lets a logged-in user with non-read-only access, reached remotely over the network, move a folder of stored credentials into their own personal space, hiding it from the organization, including administrators. The move exposes entry labels, logins, URLs, email addresses, and descriptions, though passwords protected by sharekeys stay hidden.

Written by a model

Original description

TeamPass is a self-hosted collaborative password manager. Prior to 3.2.1.2, the update_folder 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-accessible_folders set. Selecting a personal folder as the new parent passed the personal-folder guard and set personal_folder 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.

Who should check

Teams running TeamPass 3.2.1.1 or earlier, where any authenticated non-read-only user can manage folders and personal folders.

“Confirmed at HEAD 2f271cd (3.2.1.1), and present at 3.1.3.1 and 3.1.7.6.”

github.com

What to do

  1. Check whether your setup matches what the bug needs.

    TeamPass versions up to 3.2.1.1 (the advisory also confirms 3.1.3.1 and 3.1.7.6 contain the flaw) Attacker must be an authenticated user who is not read-only
  2. Upgrade to a fixed version: 3.2.1.2.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-103035 (TeamPass folder re-parenting authorization bypass), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-103035 (entry last updated 2026-11-19):
Affected:
- nilsteampassnet TeamPass: fixed in 3.2.1.2
Fixed versions: 3.2.1.2.
Conditions (all must be true for the bug to be hit):
- TeamPass versions up to 3.2.1.1 (the advisory also confirms 3.1.3.1 and 3.1.7.6 contain the flaw) (source: https://github.com/nilsteampassnet/TeamPass/security/advisories/GHSA-66q9-mxf2-xqw6)
- Attacker must be an authenticated user who is not read-only (source: https://github.com/nilsteampassnet/TeamPass/security/advisories/GHSA-66q9-mxf2-xqw6)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-103035 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-103035 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/nilsteampassnet/TeamPass/security/advisories/GHSA-66q9-mxf2-xqw6
- https://github.com/nilsteampassnet/TeamPass/commit/e022b27f99149995c90a81f83b8e0ae8b48f5a20
- https://github.com/nilsteampassnet/TeamPass/releases/tag/3.2.1.2
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-103035
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-103035"}.

Affected versions

cve.now Index

16Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.3/10CVSS 8.3
  • No patch0/5No signal

What would change the score

  • Would score about 66 if added to CISA KEV
  • Would score about 61 if CISA's SSVC rates exploitation active
  • Would score about 23 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 5

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · nilsteampassnet/TeamPass · Advisory GHSA-66q9-mxf2-xqw6
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-103035
RecordNVD · CVE-2026-103035
Other links 2
RepositoryGitHub · nilsteampassnet/TeamPass · Commit e022b27f
RepositoryGitHub · nilsteampassnet/TeamPass · Release 3.2.1.2

Questions about CVE-2026-103035

Is CVE-2026-103035 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

An authenticated, non-read-only TeamPass user can re-parent any folder into their own personal space. The plaintext labels, logins, URLs, emails and descriptions of credentials in that subtree then become accessible to them and are hidden from the organization, including administrators. Item passwords stay protected by sharekeys.

Source: github.com

Which versions are affected by CVE-2026-103035?

TeamPass: before 3.2.1.2.

Source: cve.now feed data

Am I affected, and how do I check?

TeamPass versions up to 3.2.1.1 are affected, and the advisory also confirms that 3.1.3.1 and 3.1.7.6 contain the flaw. The attacker needs an authenticated account that is not read-only, and no administrative role is required. The installed version and the account's read-only status are the things to check.

Source: github.com

How do I fix CVE-2026-103035?

Upgrade TeamPass to 3.2.1.2, the fixed version listed for this vulnerability.

Source: github.com

No corrections so far. Something wrong on this page? Report an error.