# CVE-2026-133172: Cozy Cloud cozy-stack 1.6.62 before 1.6.69 Authorization Bypass via Shared-Drive Move


- **Severity:** High 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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 19 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-92pp-cx5g-fhhr

## What is CVE-2026-133172?

CVE-2026-133172 is a high-severity vulnerability in cozy-stack, published on 19 Nov 2026. 

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

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

1 open source package ship an affected version, including github.com/cozy/cozy-stack.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `github.com/cozy/cozy-stack` | Go | `pkg:golang/github.com/cozy/cozy-stack` | From 1.6.62 | 1.6.69 |

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

Upgrade github.com/cozy/cozy-stack to 1.6.69 or later.

## Is CVE-2026-133172 being exploited?

There is no known exploitation of CVE-2026-133172 in the wild and no public exploit code.

Public exploit code:

- CVE-2026-133172 -- cozy-stack <1.6.69 Auth Bypass via Shared Drive Move (Cross-Tenant). CVSS 8.5 High. (github_poc): https://github.com/LLCForge/CVE-2026-133172

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-133172 and fix it if it is affected.

What it is: CVE-2026-133172 is a high-severity vulnerability in cozy-stack, published on 19 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-133172 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/cozy/cozy-stack (Go): affected from 1.6.62; fixed in 1.6.69

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-133172/ (Markdown: https://insights.sbomify.com/CVE-2026-133172/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-133172
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-133172
- OSV: https://osv.dev/vulnerability/CVE-2026-133172

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-133172/
Summaries are generated and may contain mistakes; the official description above is the record.
