Skip to main content
VulnerabilityPublished

CVE-2026-103035: nilsteampassnet/TeamPass · TeamPass folder re-parenting authorization bypass

Affects nilsteampassnet/TeamPassSource GCVE Database

0
Compare
Authoritative record:CVE-2026-103035· High 8.3

Not known to be exploited · CVSS 8.3 High : upgrade to 3.2.2.0 soon.

Data as of 20 Nov 2026, 15:54 UTC

CVSS 3.1 base score
8.3High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.18.3
Patch
Available – fixed in 3.2.2.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade nilsteampassnet/TeamPass to 3.2.2.0.

Affected software

ProductAffectedFixed in
Packagistnilsteampassnet/TeamPassAffected
  • <3.2.2.0
Fixed in
  • 3.2.2.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in TeamPass version 3.2.2.0 that addresses this authorization bypass. Users should upgrade to this version or later. The fix enforces authorization checks on both the target folder and the new parent folder in the update_folder action, preventing unauthorized re-parenting and ownership changes. Until patched, restrict authenticated user privileges to read-only where possible to reduce risk.

Description

TeamPass versions prior to 3.2.2.0 contain an authorization bypass vulnerability in the update_folder action. Authenticated non-read-only users can rename, re-parent, and convert any folder to personal, effectively taking ownership of another team's credential subtree and removing it from the organization's view. This occurs because the update_folder action lacks proper authorization checks on the folder ID and new parent ID. The vulnerability allows unauthorized access to credential metadata and denies access to legitimate owners. A fix is available in version 3.2.2.0.

References

Community reviews

Loading reviews…