# CVE-2026-59992: Tina: Broken Access Control: arbitrary bucket-key write/delete in `next-tinacms-s3` (and sibling production media adapters) > Authenticated CMS editors can write or delete arbitrary storage objects by bypassing mediaRoot restrictions in TinaCMS production media adapters. - **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 19 Aug 2026 - **Updated:** 21 Aug 2026 - **Also known as:** GHSA-8mq9-5fw2-5rm4 ## What is CVE-2026-59992? CVE-2026-59992 is a medium-severity missing authorization vulnerability in next-tinacms-azure, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Tina is a headless content management system. Prior to next-tinacms-s3 23.0.4, next-tinacms-dos 23.0.4, next-tinacms-azure 14.0.4, and next-tinacms-cloudinary 26.0.4, the first-party production media adapters pass attacker-controlled object keys to storage SDK upload and delete operations without enforcing the operator's configured mediaRoot. In packages/next-tinacms-s3/src/handlers.ts, createMediaHandler accepts req.query.key for a signed PutObject URL and the DELETE path uses req.query.media as the DeleteObjectCommand key. The same missing key-boundary check exists in packages/next-tinacms-dos/src/handlers.ts, packages/next-tinacms-azure/src/handlers.ts, and packages/next-tinacms-cloudinary/src/handlers.ts. An authenticated CMS editor can therefore create or delete objects anywhere the deployment's storage credential can reach, including other tenants' or non-media objects. These issues are fixed in next-tinacms-s3 23.0.4, next-tinacms-dos 23.0.4, next-tinacms-azure 14.0.4, and next-tinacms-cloudinary 26.0.4. Weakness: CWE-862 (Missing Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key) ## Which versions are affected by CVE-2026-59992? 8 open source packages ship an affected version, including next-tinacms-azure, next-tinacms-cloudinary and next-tinacms-dos. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `next-tinacms-azure` | npm | All versions | 14.0.4 | | `next-tinacms-azure` | npm | All versions | 14.0.4 | | `next-tinacms-cloudinary` | npm | All versions | 26.0.4 | | `next-tinacms-cloudinary` | npm | All versions | 26.0.4 | | `next-tinacms-dos` | npm | All versions | 23.0.4 | | `next-tinacms-dos` | npm | All versions | 23.0.4 | | `next-tinacms-s3` | npm | All versions | 23.0.4 | | `next-tinacms-s3` | npm | All versions | 23.0.4 | ## How do I fix CVE-2026-59992? Upgrade next-tinacms-azure to 14.0.4 or later. ## Is CVE-2026-59992 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59992 exists. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-59992 and fix it if it is affected. What it is: CVE-2026-59992 is a medium-severity missing authorization vulnerability in next-tinacms-azure, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59992 exists. Affected packages and fixed versions: - next-tinacms-azure (npm): affected all versions; fixed in 14.0.4 - next-tinacms-azure (npm): affected all versions; fixed in 14.0.4 - next-tinacms-cloudinary (npm): affected all versions; fixed in 26.0.4 - next-tinacms-cloudinary (npm): affected all versions; fixed in 26.0.4 - next-tinacms-dos (npm): affected all versions; fixed in 23.0.4 - next-tinacms-dos (npm): affected all versions; fixed in 23.0.4 - next-tinacms-s3 (npm): affected all versions; fixed in 23.0.4 - next-tinacms-s3 (npm): affected all versions; fixed in 23.0.4 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-59992/ (Markdown: https://insights.sbomify.com/CVE-2026-59992/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-59992 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-59992 - OSV: https://osv.dev/vulnerability/CVE-2026-59992 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-59992/ Summaries are generated and may contain mistakes; the official description above is the record.