Cozy Cloud cozy-stack authorization bypass in shared-drive move handler
- Exploited
- No known exploitation
- Fix
- Fixed in 1.6.69
- Who is exposed
- Specific setups only
Summary
Cozy Cloud's cozy-stack contains an authorization bypass in its shared-drive move handler. An attacker who can log in as a regular user and owns a shared drive can reach it remotely, name another instance's domain and any directory ID as the move source, and copy and delete the victim's file tree.
Written by a model
Original description
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.
Who should check
Teams running Cozy Cloud cozy-stack 1.6.62 through 1.6.68 (Go) with shared drives, where multiple users share one stack.
“Cozy Cloud cozy-stack 1.6.62 before 1.6.69”
What to do
Check whether your setup matches what the bug needs.
Attacker must own a shared drive on the cozy-stack server. Target is another instance hosted on the same cozy-stack server. Affected cozy-stack versions 1.6.62 up to but not including 1.6.69.Upgrade to a fixed version: 1.6.69.
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-133172 (Cozy Cloud cozy-stack 1.6.62 before 1.6.69 Authorization Bypass via Shared-Drive Move), 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-133172 (entry last updated 2026-11-19):
Affected:
- Go package github.com/cozy/cozy-stack: from 1.6.62, fixed in 1.6.69
Fixed versions: 1.6.69.
Conditions (all must be true for the bug to be hit):
- Attacker must own a shared drive on the cozy-stack server. (source: https://www.vulncheck.com/advisories/cozy-cloud-cozy-stack-1.6.62-before-1.6.69-authorization-bypass-via-shared-drive-move)
- Target is another instance hosted on the same cozy-stack server. (source: https://hackmd.io/@hieund/cve-2026-133172-cozy-stack-shared-drive-move-cross-instance-authz-bypass)
- Affected cozy-stack versions 1.6.62 up to but not including 1.6.69. (source: https://www.vulncheck.com/advisories/cozy-cloud-cozy-stack-1.6.62-before-1.6.69-authorization-bypass-via-shared-drive-move)
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-133172 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133172 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/linagora/cozy-stack/pull/5179
- https://github.com/linagora/cozy-stack/commit/983fe4b1218b8a7d83a2734b5ce2fe04227acc0c
- https://github.com/linagora/cozy-stack/releases/tag/1.6.69
- https://hackmd.io/@hieund/cozy-stack-shared-drive-move-cross-instance-authz-bypass
- https://github.com/linagora/cozy-stack/blob/1.6.68/web/sharings/move.go#L250-L263
- https://www.vulncheck.com/advisories/cozy-cloud-cozy-stack-1.6.62-before-1.6.69-authorization-bypass-via-shared-drive-move
- https://hackmd.io/@hieund/cve-2026-133172-cozy-stack-shared-drive-move-cross-instance-authz-bypass
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-133172
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-133172"}.Affected versions
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Affects Go packages
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 77 if added to CISA KEV
- Would score about 72 if CISA's SSVC rates exploitation active
- Would score about 34 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
Evidence 9
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133172 |
| Record | NVD · CVE-2026-133172 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | GitHub · LLCForge/CVE-2026-133172 · Repository |
| Other links 6 | |
| Patch | GitHub · linagora/cozy-stack · Pull request #5179 |
| Patch | GitHub · linagora/cozy-stack · Commit 983fe4b1 |
| Repository | GitHub · linagora/cozy-stack · Release 1.6.69 |
| Repository | GitHub · linagora/cozy-stack · web/sharings/move.go · L250-L263 |
| Link | hackmd.io · @hieund/cozy-stack-shared-drive-move-cross-instance-authz-bypass |
| Link | vulncheck.com · advisories/cozy-cloud-cozy-stack-1.6.62-before-1.6.69-authorization-bypass-via-shared-drive-move |
Questions about CVE-2026-133172
Is CVE-2026-133172 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 attacker who owns a shared drive on a cozy-stack server can name another instance's domain as the source or target of a shared-drive move, and the server resolves it without an authorization check. This lets the attacker read and copy another user's entire file tree from a different instance on the same stack, and delete it when the operation is a move.
Source: vulncheck.com, hackmd.io
Which versions are affected by CVE-2026-133172?
github.com/cozy/cozy-stack (Go): from 1.6.62 before 1.6.69.
Source: cve.now feed data
Am I affected, and how do I check?
Versions 1.6.62 up to but not including 1.6.69 of cozy-stack are affected, and the issue needs a server hosting several instances with the attacker owning a shared drive on it. To check, run the cozy-stack version command on the server and compare the result with the affected range.
Source: vulncheck.com, hackmd.io
How do I fix CVE-2026-133172?
Upgrade cozy-stack to 1.6.69, which is the listed fixed version.
Source: vulncheck.com, hackmd.io
Related
- CVE-2026-131293Improper Access Control in the Data Management Automation API in Splunk SOAR
- CVE-2026-131304Authorization Bypass through the REST API in Splunk AI Assistant
- CVE-2026-131297Single Sign-On Authentication Bypass in Splunk SOAR
- CVE-2026-118977Cross-node trusted facts overwrite in PuppetDB facts terminus
- CVE-2026-131286Improper Access Control through the REST API in Splunk SOAR
- CVE-2026-131262Improper Access Control through the REST API in Splunk SOAR
No corrections so far. Something wrong on this page? Report an error.