CVE-2026-133172 json
Cozy Cloud cozy-stack 1.6.62 before 1.6.69 Authorization Bypass via Shared-Drive Move
published 16h ago modified 15h ago also EUVD-2026-130207
- cvss
- 8.7
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
Cozy Cloud cozy-stack 1.6.62 before 1.6.69 contains an authorization bypass vulnerability in the shared-drive move handler that allows authenticated users to access other instances' files. Attackers owning a shared drive can name another instance's domain and any directory ID as the move source to copy and delete the victim's file tree.
Patch / fix
- Cozy Cloud cozy-stack 1.6.69
Is CVE-2026-133172 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 8.7 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N |
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Cozy Cloud cozy-stack
Classification
- Weakness
-
- CWE-639 Authorization Bypass Through User-Controlled Key
References
-
github.com
/linagora/cozy-stack/pull/5179
issue-tracking, patch
-
github.com
/linagora/cozy-stack/commit/983fe4b1218b8a7d83a2734b5ce2fe04227acc0c
patch
-
github.com
/linagora/cozy-stack/releases/tag/1.6.69
release-notes
-
hackmd.io
/@hieund/cozy-stack-shared-drive-move-cross-instance-authz-bypass
technical-description
-
github.com
/linagora/cozy-stack/blob/1.6.68/web/sharings/move.go#L250-L263
technical-description
-
vulncheck.com
/advisories/cozy-cloud-cozy-stack-1.6.62-before-1.6.69-authorization-bypass-via-shared-drive-move
third-party-advisory
Sources
- CVE List CVE-2026-133172
- NVD CVE-2026-133172
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.